Connecting an account and allowing Okou to use it are separate decisions. Sharing a Workflow or a result does not share your accounts, personal Instructions, private chats, or permission grants.
Connection, authorization, and permission
| Layer | What it controls |
|---|---|
| Connection | Which saved service account or credential you have connected. |
| Authorization | Whether that connection is available to Okou in the applicable context. Legacy Agents can require an Agent authorization. |
| Permission grant | Which named connector operations are allowed, and for how long. Review the scope shown in the request. |
Each member connects and authorizes their own accounts. A team Workflow cannot borrow its author's personal inbox or token. Workspace-installed integrations can require separate member linking.
My Okou
Use Connectors or follow the connection request in your chat. Choose the intended account, complete the service's own connection flow, and review any requested named permissions. You do not need to create a specialist Agent to connect a service.
Some accounts have additional Chat connector accounts controls. Where those controls are available, review which accounts are enabled for this Chat and which is selected. A saved connection is not automatically permission to use it in every Chat, and an account selection is not a grant of every connector operation. My Okou does not by itself enable these controls; if they are absent, use the connection and authorization flow you are shown.
Permission scope is defined by the product request and connector policy. Do not assume that a grant is isolated to one Chat or one saved account merely because you approved it there. Review the named permission and displayed duration before approving.
Legacy Agents
If your interface still has Agents, select the intended Agent and open its Authorization settings. A connection can authorize specific Agents. The selected Agent uses the executing member's connected accounts and grants, not the account of the person who published it. Removing one Agent authorization leaves other authorized Agents unchanged.
Granting and revoking access
When Okou needs permission it does not have, review the connector, operation, reason, and any account or scope shown. Choose Allow or Deny, and a duration offered by that request. Time-limited access must be renewed after expiry. Denying one permission does not disconnect the account or remove unrelated grants.
Review current access in Connectors and the permission controls the product provides. In Legacy Agents, also review the selected Agent's Authorization settings. Removing Chat access, revoking an operation, and disconnecting a saved account are different actions. Check the displayed impact before choosing one.
Credential handling
OAuth tokens and manually entered secrets are stored on the platform. For connector requests, the firewall injects the credential at the network boundary; the secret is not exposed to agent code as an environment variable.
Do not paste passwords, API keys, OAuth tokens, or client secrets into a Chat, Instructions, Workflow, or attached file. Use the connector's connection flow. Disconnecting a saved account removes that connection from future runs; it is broader than disabling its use in a single Chat.
Approval boundaries
The enforceable boundary is the connector's named permission grant. A personal Instruction or Workflow instruction does not expand access, and a generic category such as “sensitive action” does not guarantee every external write pauses in the same way.
For work that must stay human-reviewed:
- Grant read or draft access and deny final write or send access where the connector exposes them separately.
- State the review requirement in personal Instructions or the Workflow.
- Keep the final action with the human, for example by preparing an email draft or a proposed change.
Use upstream service controls too: scoped API keys, least-privilege OAuth scopes, repository permissions, and separate production credentials. Purchase approval remains separate from connecting an account.
Chats, logs, and admin visibility
Members access their own Chat threads. Publishing a Workflow, or an Agent in the legacy experience, does not publish a member's private Chats or credentials. Share conversations and artifacts only through the explicit sharing controls.
Workspace admins can see member-level usage aggregates for billing and capacity management. That does not automatically expose private Chat contents. Within your own Chat, inspect the activity record to see which connector action ran and whether it succeeded.
Review checklist
- Is the intended service account connected and available for this task?
- In Legacy Agents, is the intended Agent authorized?
- Where Chat account controls are present, is the intended account allowed and selected?
- Are only the necessary named operations allowed, for the appropriate duration?
- Does the task keep final external actions in a reviewable step?
See Connectors, Workflows, and For teams.
