DemandFlow Support Centre

DASSIGNEE: Document Assignee

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A user-to-role assignment for document management, scoped by document category and type.

DASSIGNEE: Document Assignee

A user-to-role assignment for document management, scoped by document category and type.

Default definition. This article describes the default DASSIGNEE 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 DASSIGNEE.

Entity properties

PropertyValue
Entity codeDASSIGNEE
Display nameDocument Assignee
PluralDocument Assignees
Level12020

Use cases

DASSIGNEE maps users to document roles (DROLE) within specific scoping dimensions. It uses three comboKeys: category (DTYPECAT, comboKey 1), document type (DTYPE, comboKey 2), and document role (DROLE, comboKey 3). This triple-scoping enables precise assignment rules like 'User X is an Approver for Procedure documents in the Quality Management category'. The name field is a singleuser lookup identifying the assigned person. The active checkbox allows assignments to be deactivated without deletion. When the DMS workflow engine determines who should review or approve a document version, it queries DASSIGNEE records matching the document's category and type to find users in the appropriate roles. The autoOpen:true setting streamlines creating assignments from parent context.

Fields

Role Details

FieldTypeRequiredNotes
namereference → userYesAssignee.
droleIdreference → DROLEDocument Role.
categoryreference → DTYPECATDocument Category.
dtypereference → DTYPEDocument Type.
activebooleanActive.

Relationships

  • Lookup: droleId (reference → DROLE).
  • Lookup: category (reference → DTYPECAT).
  • Lookup: dtype (reference → DTYPE).

Creating a Document Assignee via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "DASSIGNEE",
  "level":    12020,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "",
  "active": false
}

Listing Document Assignees records

GET /v1/entities/DASSIGNEE/SUB:<your-sub-id>

See also

dassigneedocumentassigneeassigneesdocumentassigneesuserroleassignmentmanagementscopedcategory

Was this article helpful?

← Back to Knowledge Base