PKPEEK Docs
Docs/Getting started

Personas and perspectives

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

All agency users

/pdcc/my-day/workspace
Live walkthrough · Personas and perspectives
/pdcc/my-day/workspace
/pdcc/account/perspective
/pdcc/preview

A persona (also called a perspective or lens) is the role you are working in right now — for example *Contracting Officer*, *Contracting Officer's Representative*, *Branch Chief* or *Acquisition Planner*. The persona reorganizes menus, My Day sections, KPIs and Scout suggestions around that job.

The golden rule — A persona never grants access. Changing persona filters and reorders work you are already authorized for. It cannot add a record, a module, a capability, a warrant or a designation, and it cannot resume or approve anything that was bound to a different persona.

Where personas come from

  • Your assigned persona set by the agency User Access Admin (agency.users.set_persona).
  • Your authority assignments: a CO warrant adds the *Contracting Officer* lens; a COR designation adds *Contracting Officer's Representative*.
  • Business users also get *Procurement* and *Budget* lenses where configured.

Only active assigned personas can be selected. Pending or expired personas appear greyed out on the approved-workspace screen and cannot be selected, queried through Scout or activated by refreshing the page.

Switch your active persona

  1. 1

    Open the account menu

    Click your initials in the top bar.

  2. 2

    Choose Active persona

    The Active persona (presentation only) selector lists only your active assigned personas.

  3. 3

    Pick a persona

    Menus, My Day and My Work re-render for that lens. Each record is rechecked before it opens.

  4. 4

    Optional: review all personas

    Open My workspace & personas (/pdcc/my-day/workspace) to see approved, pending and expired personas with their sources.

What changes when you switch

PersonaMy Work childrenAcquisitions menuTeam & Portfolio
Contract specialist (default)My Work, My AutomationsRequirements, Acquisition Actions, Contracts & Orders, Market Research, Strategy & Lessons—
Contracting OfficerAssigned Jobs, Packages & Reviews, CalendarContracts & Orders, Acquisition Actions, Strategy & Lessons—
Contracting Officer's RepresentativeAssigned Jobs, Deliverable Reviews, CalendarContracts & Orders, Deliverables—
Branch Chief / SupervisorAssigned Jobs, Reviews, CalendarRequirements, Actions, Contracts, Market ResearchTeam Workload, Assignments, Portfolio Overview, Exceptions, Resources
Division leader / DirectorDecisions & Follow-ups, CalendarRequirements, Actions, Contracts, Market ResearchOffice Overview, Teams & Workload, Portfolio, Organization, Exceptions
Executive / HCADecisions & Follow-upsRequirements, Actions, ContractsLeadership Overview, Portfolio, Significant Exceptions
Program / requirement ownerRequired Inputs, Reviews, CalendarMy Requirements, Contracts & Orders, Deliverables—
Budget reviewerMy Work, My AutomationsRequirements, Actions, ContractsOperational Views, Milestones & Bottlenecks
Tip — Persona menus only reorder and relabel destinations the server has already authorized. If a module is not enabled or you lack the capability, it does not appear in any persona's menu — and every page and API rechecks access anyway.

Perspectives in onboarding and Scout

  • During onboarding you choose a starting perspective (/pdcc/account/perspective); it can be changed later in preferences.
  • Scout has its own persona selector. Switching it never expands data access or executes a pending proposal — each proposal stays bound to the persona that reviewed it.
  • An automation keeps the execution identity and scope it was approved with, even if you later change persona.