Skip to main content
Every MCP connection acts as one Floral user in one workspace. Floral checks the user’s active membership and current access again when each tool runs.

​
Personal access token scopes

Token creation offers these scope pairs: New keys start with the available read scopes selected. Remove any read area the client does not need. Add a write scope only for an intended write workflow.

​
Write behavior

A write made with a personal access token does not pause for the approval dialog used by the in-app Assistant. The MCP client can execute any write allowed by the key and the user’s current permissions.
Use a separate key per client, give it a short expiry, and avoid “no expiry” unless the environment has its own rotation process. Test with read-only access first. OAuth connections are read-only. Use a personal access token only when the client needs writes and can protect a bearer secret.

​
Credential handling

  • Store the full key in the client’s secret storage.
  • Never put it in source control, a prompt, a Source, or ordinary logs.
  • Revoke it immediately if it appears in copied output or screenshots.
  • Disconnect unused OAuth clients and revoke keys for retired devices.

​
Audit use

Open Settings > Assistants > Logs. Administrators see workspace-wide tool use; members see their own. Review the tool name, access type, surface, status, and time. Also inspect the changed record after a sensitive write.