Skip to main content
Skip table of contents

Role Definitions

Authorization

IDMS utilizes a defined set of roles, each with specific permissions and functions, to manage various aspects of identity, credentialing, and system operations. Understanding the roles is crucial for comprehending workflows and assigning appropriate responsibilities within the IDMS.

System Roles and Permissions

The following table details each role and its corresponding responsibilities:

IDMS Role

Permission

ApplicantCreatorOperator

Enables an operator to create an Applicant within the IDMS database. This is useful when the applicant information is not in a directory that the IDMS can retrieve the information from.

Requester

Creates credentialing requests. This role is permitted to start the process by creating a request for a user. Specifically, the requester can either retrieve a user from an existing data repository (such as active directory) or manually enter the user.

EnrollmentOfficer

Captures biometric data. This role captures the identity attributes (fingerprints, photo ID details) and identity documents for a given user. This role is allowed to retrieve users that have a valid credential request (users that are in the REQUESTED state)

ApprovalOfficer

Approves the identity request. This role will make a decision if the enrolled user can receive a credential. Specifically, this role can retrieve the users in the [IDACQUIRED] state. When this role approves the user, the information is sent to the credential management system.

CredentialProducer

Prints and encodes the credential. This role will print and activate the card. This role can retrieve users in the APPROVED and obtain the photo and other printed items.

ReportingOfficer

Has access to a comprehensive suite of reports, primarily focused on transaction information and various system components. This allows them to monitor and analyze different aspects of the system's operations.

  1. View Queues: Access reports detailing the status and information of items currently in various processing queues, providing insights into workflow progress and bottlenecks.

  2. Review User History: Generate reports on individual user activities and historical data, which is crucial for auditing and tracking user interactions within the system.

  3. Examine Events: Access logs and reports of system events, offering an audit trail of actions, changes, and anomalies within the platform.

  4. Analyze Certificates: Pull reports related to certificates, including their issuance status, expiry, and other relevant details, essential for credential lifecycle management.

  5. Monitor Devices: View reports pertaining to registered devices, which may include their status, type, and associated users.

  6. Track Operators: Generate reports on operator activities, providing oversight into administrative actions and changes made by system operators.

  7. Manage Subscriptions: Access information and reports regarding system subscriptions, potentially including status and details of subscribed services or users.

DerivedApplicant

Requests a derived credential.

DerivedRequestOfficer

Official that requests derived credential.

DerivedApprovalOfficer

Approves the derived credential.

SystemManager

Role is responsible for comprehensive system configuration and management. This goes beyond general configuration to include detailed settings across various critical aspects of the IDMS.

  1. Manage System Connections: Configure and maintain connections to external systems and services, which are vital for the IDMS's interoperability.

  2. Define Credential Types: Set up and modify the various types of credentials that can be issued by the system (e.g., different physical cards, digital certificates).

  3. Set Up Scheduling: Configure automated tasks and scheduled operations within the IDMS.

  4. Configure ID Proofing: Define and manage the processes and settings related to identity verification and proofing.

  5. Manage Operators: Administer user accounts and permissions for system operators, controlling who can perform specific administrative tasks.

  6. Manage Process Locks: Handle and resolve any locks on system processes, which might occur during concurrent operations.

  7. Configure Automations: Set up and manage automated workflows and rules to streamline various system tasks.

  8. Manage Features: Enable or disable specific functionalities and features of the IDMS as needed.

  9. Configure Printers: Set up and manage the printers used for credential issuance.

CredentialIssuer

Binds and encodes the credential. This role will perform a face to face personalization of the credential.

OnDemandCredentialRequestOfficer

Adds records for immediate credential issuance.

CryptoDataManager

Encrypts data with the HSM (Hardware Security Module).

CredentialManager

Manages an existing PIV (Personal Identity Verification) Credential.

BulkCredentialOperator

Manages credentialing automation.

CredentialUpdateOfficer

Permits updates of existing credentials.

DigitalSigner

Performs acknowledgement signing.

CredentialDataUploadOfficer

Enables the upload of existing PIV credential information into IDMS.

CredentialRecycleOperator

Performs recycle of terminated devices.

CredentialInventoryManager

Enables the credential inventory to be managed and orders to be created.

NotificationService

Service submitting credential notifications.

FacilitiesManager

Manages rooms and visitor check-ins.

IdStatusViewer

Enables the retrieval of the processing status for a user.

ExpungementOfficer

Enables the expungement of a record.

CredentialTerminationOfficer

Enables the termination of credentials.

ApplicantCreatorOperator

Enables the creation of an applicant within the IDMS

Example Role Assignments

image-20250520-133457.png

The enrollment officer and credential issuer cannot be assigned to a single operator at the same time. This ensures the operator that captures the identity information is separate from the operator distributing the device.

image-20250520-133523.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.