DROLE: Document Role
A document management role defining review/approval permissions, SLA deadlines, and escalation paths.
DROLE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches DROLE.Entity properties
| Property | Value |
|---|---|
| Entity code | DROLE |
| Display name | Document Role |
| Plural | Document Roles |
| Level | 12020 |
Use cases
DROLE defines the roles that participate in the document review and approval workflow. The type field (None, Reviewer, Approver, Both) determines what workflow actions users assigned to this role can perform. SLA tracking (slaDays) with escalation (escalationRole, a self-referencing DROLE lookup) supports automated deadline management - if a reviewer does not act within the SLA, the system can escalate to the fallback role. The canComment and canApprove checkboxes provide granular permission control beyond the type classification. The active flag allows roles to be deactivated without deletion, preserving historical audit trails. DROLE works with DASSIGNEE to create the mapping of users to roles for specific document types/categories, forming the basis of the DMS workflow participant selection.
Fields
Role Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Role Name. |
description | text (multi-line) | Explain the purpose of this document role | |
type | enum | Yes | Valid ids: none (None), reviewer (Reviewer), approver (Approver), both (Reviewer + Approver). |
Workflow Settings
| Field | Type | Required | Notes |
|---|---|---|---|
slaDays | number | Target time for review/approval before escalation | |
escalationRole | reference → DROLE | Fallback role if this reviewer doesn't act in time | |
canComment | boolean | Can Comment. | |
canApprove | boolean | Can Approve. | |
active | enum | Yes | Valid ids: 0 (No), 1 (Yes). |
Relationships
- Lookup:
escalationRole(reference →DROLE).
Creating a Document Role via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DROLE",
"level": 12020,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"type": "none",
"active": "0",
"description": "Example value"
}Listing Document Roles records
GET /v1/entities/DROLE/SUB:<your-sub-id>