Approvals and permissions
Choose when app tools need approval, review exact actions, and manage saved tool rules.
The permission control in the composer determines how Fluso uses connected apps in that chat. It does not connect an account or select an app for an Agent.
Choose a mode
| Mode | Behavior |
|---|---|
| Ask me first | Ask before actions that are not already allowed by tool or connection rules |
| Allow everything | Use connected app tools automatically, while respecting denied tools and organization restrictions |
Read-only tools follow each connection's settings. Ask me first therefore does not guarantee a prompt for every read. If a particular action must always need review, check that tool's saved rule and the chat's mode.
Select the hand or open-lock control in the composer to change the mode. Before the first message, a new chat's choice is pending until the chat is created.
For an external send, ask Fluso to prepare a draft, review its recipients and contents, and authorize the send when ready.
Set the default
Open Settings → Approvals & permissions. Auto-approval sets your default across desktop, web, and Telegram.
Chats where you explicitly picked a mode keep it. Other chats follow the current default, including existing chats without an override. A Settings change does not itself decide an approval already waiting.
Review an approval card
The card identifies the connection, tool, and arguments. Expand Arguments when the summary is not enough to judge the action.
- Allow once permits this pending tool call with these exact arguments.
- Always allow this tool saves a rule for future calls to that tool. It is broader than this one request.
- Deny rejects this request without saving a permanent deny rule.
- Cancel cancels the pending approval.
If the app needs authorization, finish its connection flow. Missing account access and permission to run an action are separate decisions.
Expired or changed requests cannot reuse an old approval. If an approval is no longer actionable, inspect the conversation before asking for another attempt.
Manage saved tool rules
Open Plugins → MCP, select the connection, and open its tool permissions. Rules can be Allow, Ask, or Deny. The connection also has Auto-approve read-only tools for tools classified as reads.
Explicit tool rules take precedence over read-only defaults. The chat's Allow everything mode can allow actions that would otherwise ask; it cannot override a deny. Organization restrictions and an Agent's saved app restrictions still apply.
An Agent's Allowed connector setting only permits use of that connection. It does not override a tool deny, supply credentials, or approve a particular pending action.
When something is blocked
| Situation | Check |
|---|---|
| Changing Settings did not change a chat | That chat may have its own explicit mode |
| A read ran without a card | Check saved allow rules and the connection's read-only setting |
| Another tool still asks after Always allow this tool | The saved rule applies to that tool, not every tool on the connection |
| No approval can unblock the action | Check Agent capabilities, saved denies, organization restrictions, and connection status |
| A delegated session waits | Review its approval in the session, main conversation, or Inbox |
See Apps & MCP for connecting accounts and Setup and capabilities for selecting them for an Agent.