Privacy modes and approvals
Choose the conversation mode and access that fit the work. Memory controls, tool approvals, and external service access address different boundaries.
Memory modes
| Mode | Reads existing memory | Writes new memory |
|---|---|---|
| Normal conversation | Can read | Can write |
| Temporary | Suppressed | Suppressed |
| Incognito | Allowed | Suppressed |
Restricted conversations also skip after-turn lesson writing. Neither mode is a promise that model providers or connected services keep no records. Avoid including secrets in ordinary chat material.
Before approving an action
Read the requested tool, destination, and scope. Confirm the account and file when names are similar. If the request is broader than the task, narrow it or provide the missing context.
Plan mode
Use Plan this first when you want a reviewed plan before execution. Edit or comment on the plan, then approve and run it, or cancel. The native runtime’s task-mode gate applies independently of approval. External agent behavior can differ; see limitations.
Connected services
Use Apps and Connections to manage service access. Store secrets through the credential controls rather than in prompts, skills, or Knowledge documents. Removing a connection can interrupt work that depends on it; inspect outstanding runs when changing access.
The learning-site assistant
The assistant on this site answers documentation questions. It cannot access your Gideon account, run tasks, or change settings. Its conversation is held in the current browser session, and questions are sent to the configured model service to produce answers. Do not paste credentials into it.