Permissions
What a connected assistant can read, change and run, what it cannot, who can publish, and what is logged.
Scope
The connection acts as you, in the workspace you picked at sign-in, with the permissions your account has there. It cannot read or change another workspace. Every person connects with their own account; there are no shared connections.
Data
A connection reads what its operations ask for, in the workspace you picked: the workspace's configuration, customer and test conversations, workflow runs, and the pages and API traffic captured by a paired browser extension.
Algomo receives the operations your assistant sends and nothing else from it. It does not read the assistant's chat history, memory or files.
See Algomo's privacy policy and terms.
Reads
Reads have no side effects. Third-party connections (a calendar, a CRM credential) are listed by name and never with their secrets. Creating or changing a credential happens in the dashboard.
Changes
Changes to configuration (chatbots, goals, tools, workflows, custom agents, cards, knowledge-base pages, connectors, booking calendars, conversion rules) are staged in an edit session and are live only after the session is published.
Four kinds of write apply at once, with no session: workspace settings (the messenger's appearance and domains), tasks, onboarding answers, and clearing a workflow step's cached results. The last deletes cached results and no configuration.
Publishing
Publishing goes through the algomo_publish tool, which the server marks destructive. Claude and ChatGPT confirm it with you by default. If you set that tool to Always allow in your client, the assistant can publish on its own. That is a setting you change in the client; the default is to ask.
Anyone in the workspace can see every session, in the dashboard and through a connection, so two people can work on one change and either can publish it.
Running things
The algomo_run tool runs a workflow, runs a custom agent, sends a test message to a chatbot, verifies website access, or drives your paired browser extension. A workflow run does what the workflow does, including sending an email or a message where the workflow says so. The tool asks before it runs for that reason.
Visitors
A connected assistant never talks to your visitors. It configures, tests and reviews the agent on your website; visitors talk to that agent through the messenger widget, in Algomo's own runtime. The widget can be embedded on any web page: a marketing site, a web app or a docs site. Test messages the assistant sends are recorded as test conversations and never appear in your customer list.
Audit
Algomo logs every operation a connection runs, with the user, the workspace and the fields it was called with, secrets removed. The log is not shown in the dashboard. Algomo's support can look an operation up on request; see Still stuck.
Disconnecting
Remove the connector in your client. The sign-in it held expires on its own and is not renewed. Sessions the assistant staged stay in the workspace until someone publishes or discards them, in a chat or in the dashboard.
The security page covers Algomo's security practices in general. This page covers the connection only.
Tools and requests
A connected assistant sees four tools, split by what each does to the workspace. Each takes the same request and refuses an operation that belongs to another tool.
Set up a new workspace
A workspace that has not been configured yet is set up from the chat, in two stages, with the browser extension as the assistant's way of reading your site.