Document control: folders, versions, approval, transmittals and retention
Store documents in folders, control versions and check-out, move files through review and publishing, issue transmittals, share links and recover deleted items.
On this page
Process at a glance
- Set up categories and foldersAdministratorDocument categories exist; folders are created in Browse.
- Upload and organise filesDocument controllerFiles sit in folders with versions and tags.
- Complete the registerDocument controllerDocument number, revision, type, confidentiality and dates are filled in.
- Review and publishApproverThe file is approved or rejected, then published.
- Issue to external partiesDocument controllerA transmittal records what was sent, to whom and why.
- Track due actionsOwnerFollow-ups show the next action and due date per record.
- Audit and recoverAdministratorAccess log shows every action; Trash restores deleted items.
#Purpose and scope
This chapter covers the document life cycle in Document Management: organising files, versioning and check-out, the review and publishing states, transmittals, sharing, retention rules and recovery. Other modules also attach files to their own records; those files are stored in the same document store and appear under automatically created attachment folders.
#Before you start
- Define document categories in Categories (code, name, colour, icon, sort order).
- Decide who may approve documents. Approvals and publishing use the workflow engine (see “Workflow automation”); the publishing workflow is linked to the record type DMS-DOC and transmittals use DMS-TRANS.
- Check the denied upload extensions with your administrator. The upload guard rejects files on the extension denylist and files whose content is an executable, whatever their extension.
#1. Organise and upload files
- Open Browse. Create folders in the tree, then upload files into a folder.
- Open a file to see its properties, versions, comments and tags. Details and grid views are available, and you can filter by lifecycle status.
- Folders can be renamed, copied, moved, pasted and downloaded as a ZIP. Deleting a file or folder sends it to Trash.
- Folder permissions are set per role (view, upload, download, delete, folder upload, folder download, edit metadata, check out, approve, share, print, comment).
#2. Versions and check-out
- Upload a new version from the file. The previous version stays in the history and the new one becomes the latest version, keeping the folder, lifecycle status, category and custom metadata.
- Check a file out before editing it offline. Only one user can hold a check-out at a time.
- Check it in when finished. Uploading a new version as the person who holds the check-out also clears the check-out.
| Situation | Result |
|---|---|
| A second user checks out a file already checked out | Refused (conflict) |
| The same user checks it out again | Refused |
| Check-in by someone who does not hold the check-out | Refused (forbidden) |
| New version uploaded while another user holds the check-out | Refused (conflict) |
#3. Complete the document register
- Open Document register. Search by name, document number, code or author, and filter by status, type or confidentiality.
- Double-click a row to edit: name, document number, revision, status, type, confidentiality, author, category, department, source, language, physical location, effective, expiry and review dates, description.
- The footer shows the number of documents, the total size and counts per status and type.
| Field | Values |
|---|---|
| Document type | Contract, Drawing, Specification, Procedure, Form, Report, Certificate, Invoice, Manual |
| Confidentiality | Public, Internal, Confidential, Restricted, Secret |
#4. Lifecycle, review and publishing
- A new file starts as Draft. In Browse choose Submit for publishing on a draft file and confirm. This starts the workflow linked to DMS-DOC and sets the file to Review.
- When the workflow is approved the file becomes Published. When it is rejected the file returns to Draft and the reason is appended to its description.
- Other status changes follow the allowed moves in the table below; a move that is not allowed is refused and the allowed list is shown.
| From | Can move to |
|---|---|
| Draft | Review, Published, Archived |
| Review | Draft, Approved, Rejected |
| Approved | Published, Archived |
| Rejected | Draft, Review |
| Published | Archived, Review |
| Archived | Published, Destroyed |
| Destroyed | No further moves |
#5. Per-reviewer approvals
- Open Approvals. Each row shows the file, who requested it, the approver, status, comments and dates.
- The designated approver chooses Approve or Reject and may add a comment. Only pending approvals assigned to you can be decided, and a decided approval cannot be decided again.
- Deciding also sets the file’s lifecycle status to Approved or Rejected.
#6. Transmittals
- Open Transmittals and create one with a subject, from and to company, attention, sent by (required), sent and due dates, purpose, priority and remarks.
- The Items column shows how many documents are on the transmittal.
- Track the status through draft, review, approved, sent, acknowledged and closed.
| Field | Values |
|---|---|
| Purpose | For approval, For review, For information, For action, As requested |
| Priority | Low, Normal (default), High, Urgent |
#7. Follow-ups
- Open Follow-ups and add one for an official document, a document transmittal, a shipment or a shipping container.
- Set the owner, next action, due date, priority (low, normal, high, urgent) and, if needed, who to escalate to.
- Move the status through open, in progress, blocked, completed or cancelled.
#Other tools in this module
| Screen | Use |
|---|---|
| CAD viewer | View CAD drawings in the browser (view only). |
| Plan markup | Redline and comment on CAD plans, PDFs and images. |
| DocSync pairs | Folder sync pairs; direction, enabled and size limit are controlled centrally. |
| DocSync registrations | Registered DocSync desktop agents and their status. |
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Document controllers, project and quality teams, and administrators
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:article/guide/document-control
Was this helpful?