Docs/Administration

Role assignments and authority

Keep application roles separate from contract-specific warrants and designations; record and validate authority (UA03).

User Access Admin

/pdcc/admin/users?screen=UA03

Live walkthrough · Role assignments and authority

Role assignments and authority — /pdcc/admin/users?screen=UA05 — /pdcc/admin/users?screen=UA05

An app role decides which commands someone may run. Authority — a CO warrant, a COR designation, a delegation — decides whether a specific legal decision is valid. The two are recorded and checked separately.

Authority record

User: e.g. Casey Park.
App role: e.g. Contracting officer lens.
Authority reference: e.g. DEMO-CO-MR014.
Scope: e.g. MR-026-014 report decision only, or a contract, or all (*).
Limit: Dollar limit for warrants (e.g. USD 5,000,000).
Effective period: e.g. 1 Oct to 31 Dec 2026.
Evidence: Verified authority record (synthetic in the demo).

1
Open the user
Users & Access › select a user.
2
Record authority
Type (CO warrant / COR designation), scope, limit, dates and evidence.
3
Review effective access
Test what the user can now do.
4
Revoke when it ends
Revocation affects live requests, queued actions and downloads.

Heads up — Role labels do not establish legal authority. For each decision the app validates scope, dates, limits, appointment evidence and separation of duties. A COR designation verified here is what contract team assignment needs before COR access is created.

Related guides

Contract team assignment

How a contract is assigned to its contract specialist, contracting officer and COR — proposals, designation evidence, confirmation and what each role can then do (CT05).

Users and access

Manage agency-approved membership, provision trusted identities and map organization relationships (UA01, UA02, UA07).

Access requests, effective access and access history

Approve or return bounded requests without self-elevation, simulate effective access, and review grants, expiry and removals (UA04–UA06).