Modules: Core and optional

The Agency App is modular. Core is always present; optional modules add native workflows on top of it. Every module requires only Core, so any combination works — and a missing module removes a native workflow, never the underlying business need.

Four independent gates

A module is usable only when all of these are true, and each is managed separately:

1. Commercial entitlement — purchased for the agency (set in the PEEK Administration Center).
2. Agency enablement — activated by the Agency App Admin after readiness checks.
3. Your permissions — your roles and scopes include the capability.
4. Policy and runtime — agency policy allows it and the service is available (e.g. SI is not paused).

When a module is absent

• No Market Research? Register an external research package through Core intake and accept it into planning (linked work).
• No Acquisition Planning? Requirements and external work still flow through Core.
• No Sigma? Scout is hidden; every workflow has a manual path (e.g. manual assessment in research).
• No Studio? Standard Core pages remain fully usable.
• No Agentic Operations? Deterministic Core reminders and manual tasks keep their baseline behavior.

When a module becomes available

Users see a New capabilities available notice. Adoption is optional: you can start new work, supplement existing work, or keep your current workflow. Activation never grants records, migrates existing work, changes accepted baselines or replays notifications.