Settings Tab
The Settings tab contains user-level preferences and, for project admins, the full project configuration. Project settings control how documents are numbered, which fields are required, how file names are validated, and how external systems receive event notifications. Changes to project settings apply to new records; existing records retain the values they were created with.
My Preferences
Available to all users. Controls your personal display and communication settings:
| Setting | Description |
|---|---|
| Display name | Your visible name across reviews, transmittals, and correspondence. |
| Timezone | Controls all date/time display in Workflows. |
| Date format | Regional date format preference (DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD). |
| Language | Interface language (where translations are available). |
| Notification preferences | Per-event email frequency. See Notifications. |
Project Settings (Admin)
Visible and editable only by project admins and org admins.
General
| Setting | Description |
|---|---|
| Numbering prefix | A short alphanumeric prefix prepended to every document number in this project (e.g., PRJ-A). |
| Default review days | The default step duration (in calendar days) used when no SLA is specified in the review matrix or template. |
| Mandatory reviewer | When enabled, workflows cannot be created without at least one named reviewer. |
| Reset review status on new revision | When enabled, uploading a new revision resets the document's review status to Draft. |
Document field configuration
Project admins can add, edit, reorder, and deactivate the pick-list options for each document metadata field. Access via Settings → Document fields.
| Field configurable | Options you can manage |
|---|---|
| Document types | Add new types (Drawing, Specification, Report, etc.), rename, set a type code, reorder. |
| Disciplines | Add disciplines (Structural, Mechanical, Civil, etc.), set discipline code, reorder. |
| Zones / areas | Add zone options with zone codes. |
| Stages | Add programme stages or delivery phases. |
| Packages / contracts | Add work package or contract references as selectable options. |
For each option: set a Label (displayed in the UI), a Code (used in auto-numbering), and an Active toggle (inactive options are hidden from the pick-list but remain on records that used them).
Mandatory fields
Configure which document metadata fields must be completed before a document upload or edit can be saved. Access via Settings → Mandatory fields.
| Behaviour | Detail |
|---|---|
| Mandatory fields | Upload and edit forms show a red asterisk; save is blocked until all mandatory fields are filled. |
| Per-document-type overrides | Different mandatory field sets can be configured for each document type (e.g., drawings require Zone; reports do not). |
File naming pattern
Enforce a project-level filename format to prevent non-standard file uploads. Access via Settings → File naming.
| Setting | Description |
|---|---|
| Pattern (regex) | A regular expression that all uploaded filenames must match. Leave blank to allow any filename. |
| Error message | A human-readable message shown when the filename fails validation (e.g., "File name must follow the format DIS-TYPE-NNNN.pdf"). |
| Apply to | New documents only, or new documents and new revisions. |
Webhook configuration
Webhooks let Workflows push real-time event notifications to external systems (project management tools, data lakes, custom dashboards). Access via Settings → Webhooks.
Configuring a webhook:
- Go to Settings → Webhooks → New webhook.
- Enter the Endpoint URL (HTTPS required).
- Enter a Shared secret used to sign the webhook payload (HMAC-SHA256). The receiving system uses this to verify authenticity.
- Select which Events to subscribe to (see event list below).
- Toggle Active and save.
Supported webhook events:
| Event | Fires when |
|---|---|
workflow.created | A new workflow is started on a document. |
workflow.completed | A workflow reaches its final state (approved, rejected, or auto-completed). |
workflow.step_completed | Any workflow step is completed by an assignee. |
document.created | A new document record is added to the register. |
document.status_changed | A document's status is changed. |
transmittal.issued | A transmittal is formally dispatched to recipients. |
transmittal.acknowledged | A recipient acknowledges a transmittal. |
Delivery and failure handling:
- Webhooks are delivered with a 5-second timeout. If the endpoint returns a non-2xx status or times out, delivery is retried up to 3 times with exponential backoff.
- The webhook delivery log (in Settings → Webhooks → Delivery log) shows each delivery attempt, response status, and payload.
- After 10 consecutive failures, the webhook is automatically deactivated and a notification is sent to the project admin.
Related
- Notifications — per-user notification preferences
- Access Control Groups — group and permission management
- Review Matrix — auto-routing rules per document type