Browse the Help Center
Configure document settings
Set up the reference lists behind every document: types, statuses, disciplines, suitability codes, confidentiality levels, and custom meta fields.
1 min read
Every document in every project carries values from a handful of workspace lists. Those lists live in Projects settings, and getting them right early means every register in the workspace speaks the same language.
The lists and what they control
| List | What it controls |
|---|---|
| Document types | The kinds of document your teams register: drawings, reports, schedules, specifications. |
| Document statuses | The lifecycle stages a document moves through, shown as a badge in every register. |
| Document disciplines | The trades documents belong to, such as Structural or Electrical. They also feed the Document Reference. |
| Suitability codes | What a revision may be used for, like For Construction or For Information. |
| Confidentiality levels | How restricted a document is and who can open it. |
| Custom meta fields | Extra fields your organisation needs on documents, beyond the built-in ones. |
Edit a list
Most of these lists are inline-editable tables. There is no separate edit form: you work directly in the table, like a spreadsheet.
- 1
In workspace settings, open Projects settings and pick a list, for example Document disciplines.
- 2
Click a cell to edit it in place. Type the new value, or pick from the dropdown where the cell offers one.
- 3
Changes save per row. Add new entries at the top of the list, and use the row menu to remove one.
Where these values show up
Everything you define here surfaces in the register: statuses as badges, disciplines and suitability codes as columns and filters, confidentiality levels as access controls. To see it from the project side, read Suitability, disciplines, and references and Document statuses explained.
These lists are workspace-wide
A change here reaches every project at once. Renaming a status or removing a discipline affects documents that already use it, so agree changes with your project leads before you make them.
Was this page helpful?
Need help? Contact support.
See what shipped in the changelog.
Questions about pricing? Talk to sales.
Something down? Check the platform status.
Found a bug in the product? Report an issue.
Missing something? Request a feature.