This operating map explains each AgencyOS input group, why it exists, what fictional or masked test information may be used, and what must never be entered. It does not authorise real customer data.
Use only fictional or masked, non-sensitive planning information. The exact approved staff account email needed to sign in or join is the sole stated identity exception.
Permitted solely for controlled, non-sensitive pilot planning.
Limited to the approved teammate email required for controlled access.
Not saved as a business record, but the same prohibited-data rules still apply.
Use these fields to test a fictional enquiry from first capture through internal follow-up.
Use quote fields to test manual pricing and a fictional client-facing plan without live supplier or customer data.
Use operations fields to rehearse internal work and a fictional manual ledger after a sample quote is accepted.
The approved staff sign-in email is the pilot’s sole stated identity exception; every other value stays fictional, masked or structured.
A field does not become safe merely because it is temporary. Apply the same pilot-only boundary before typing.
Request keys, versions, internal record and membership identifiers, cursors, timestamps, accountable actor references and calculated totals are generated, derived or selected by AgencyOS. They are not places to add customer information and do not widen the pilot's permitted data scope.
This map does not inspect, redact, retain or delete what a user types. Approval of the comprehensive data scope has not been recorded, and the legal-governance, lifecycle, security, resilience and controlled go-live gates remain open.