PKPEEK Docs
Docs/Administration

Users and access

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

User Access Admin · Agency App Admin

/pdcc/admin/users
Live walkthrough · Users and access
/pdcc/admin/users
/pdcc/admin/users?screen=UA02
/pdcc/admin/users?screen=UA07

Users & Access is for the delegated User Access Admin. Administration children appear only for users holding each delegated grant; user, connection, SI and workflow administration are granted independently with no self-elevation.

Heads up — There is no public registration. PEEK or vendor employees have no standing agency data access; support exceptions need separate agency approval and an expiry. Reviewing an identity request does not grant a default persona or full-app administration.

Directory actions

ActionCommand
Invite / provision an approved identityagency.users.invite, agency.users.activate
Assign app rolesagency.users.assign_roles
Grant or revoke data scopeagency.users.grant_scope / revoke_scope
Set personaagency.users.set_persona — presentation only
Record or revoke authorityagency.users.record_authority / revoke_authority
Set handoff grantsagency.users.set_handoff_grants (submit, decide, review change)
Remove a grantagency.users.remove
Attest an access reviewagency.users.attest_review

Provision an approved identity (UA02)

  1. 1

    Validate the identity binding

    Identity issuer (agency-approved IdP) and verified opaque subject ID.

  2. 2

    Confirm sponsor

    Agency sponsor (e.g. Maya Ortiz).

  3. 3

    Set requested assignment

    e.g. Research owner, assigned acquisitions.

  4. 4

    Attach approval evidence and expiry

    Agency authorization reference; expiry per agency policy.

  5. 5

    Activate

    Only approved assignments are activated.

Note — Never rely on email domain, name, employer or CAC alone. Validate issuer and stable subject, sponsor, delegated scope and independent approval.

Organization and responsibility mapping (UA07)

Supervisory source
Agency-approved directory.
Funding assignments
SAP authoritative mapping — never overwritten locally.
Awarding office
Contract source office.
Unmatched role
Source-owner review required.

Supervisory, awarding, funding and program relationships are validated independently. Effective-dated mappings need source-owner confirmation; organization grants are never inferred from a title.

Related guides

Role assignments and authority

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

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).

Personas and perspectives

How the active persona and work perspective shape menus, My Day and Scout — and why they never grant access or authority.