Context is given,
not assumed.
Choose the Knowledge sources each agent may read. Drafts can point back to source material, so a person can check the information behind the work.
SOURCE GRANTS / CITATIONSCONTROL & OWNERSHIP
Give AI a job.
Keep a hand
on the work.
Decide what an agent can read, what it may do and what needs a person. Keep the context behind a decision close to the work itself.
Explore the boundaries
DEFINED ACCESS
CLEAR BOUNDARIES
01 / EVERYDAY PRODUCT CONTROLS
Useful freedom.
Clear boundaries.
The controls are part of the working experience. They help your team understand what happened and decide what happens next.
Context is given,
Review the thing
that will go out.
Outward work waits for human approval. The review is tied to the actual draft; agents cannot approve outward work.
ACTUAL DRAFT / HUMAN APPROVALGive internal work
the right permission.
Use Ask, Notify or Allowed where the action supports it. The internal-work setting does not remove human approval for outward work.
ASK / NOTIFY / ALLOWEDSee the decision
with the work.
Follow the work and its decision in the Record. Owners can export company data from Settings, keeping the company’s work within reach.
RECORD / COMPANY EXPORT02 / PRACTICAL LIMITS
Your working day.
Your allowance.
Useful AI should be something your business can understand and manage.
Keep an eye on the cost.
Set a monthly AI allowance and follow usage in dollars. New work stops at the limit; work already running can finish. An allowance is not a guarantee of an exact final total.
Respect the schedule.
Set company quiet hours. Approved outward work waits until delivery is allowed, so a prepared message can respect the working day.
03 / THE ENVIRONMENT MATTERS TOO
Stricter requirements?
Start there.
Product permissions and deployment requirements are different parts of the same conversation.
For private environments, government contractors and teams with additional operating requirements, we work through the data paths, administrative access, AI model access, external services and responsibilities before choosing a setup.
A deployment proposal should identify the required controls and how they will be checked. This page describes product behavior and our approach; it is not a certification or a promise that every environment has the same controls.
Explore deployment and responsibilities04 / A CLEAR HANDOFF
Your work should
stay within reach.
If your needs change, you should know what you can take with you and who is responsible for the transition.
COMPANY DATA
Export the work.
Company owners can export company data from Settings. Review the export with your team before changing environments or ending access.
CUSTOM SOFTWARE
Define the delivery.
Your scope sets out source delivery, documentation and ownership for a custom build. Platform and third-party terms remain separate.
THE OPERATION
Know the handoff.
Agree on access, recovery, maintenance and any transition support as part of the operating arrangement.