Skip to main content
Strawberry is powerful because companions can use real context and tools. Use that power with clear boundaries.

​
Start read-only

For a new workflow, start by allowing reading and drafting. Add write actions only after you trust the prompt and output. Good default:

​
Use permission settings

Review:
  • strawberry://settings/ai-permissions
  • strawberry://settings/integrations
  • Per-integration tool permissions
  • Folder access prompts
  • Routine permissions
Permission settings cover the actions listed for each app. Some reads do not have a separate control, and saved allowances still apply in Ask Always mode. Review the connected account itself when deciding what information a companion can access.

​
Be careful with always-allow

Only use Always allow for low-risk actions you understand. Avoid always-allow permissions for tools that send messages, change records, delete data, invite users, or spend money.

​
Treat shared companions as editable

Companion sharing currently grants edit access. Recipients can update settings, memories, and skills until you stop sharing. Do not put sensitive files or private instructions into a companion you plan to share broadly. Anyone with a public file link can view the current synced file or folder until you revoke the link. Later edits and files added to a shared folder can become public through the same link. Share a separate, unchanged copy if you want to publish a fixed version. Revoking a link does not remove downloaded copies.

​
Destructive actions

Review destructive actions carefully:
  • Account deletion
  • Team deletion
  • Clearing cookies and site data
  • Disconnecting app accounts
  • Removing members
  • Revoking shared access
  • Deleting files

​
Human review checklist

Before approving an important action, check:
  • Which account or profile is involved
  • Which external app will be changed
  • Whether the output cites sources
  • Whether the companion is acting on current data
  • Whether the action can be undone