Skip to main content
Claude acts as you. Every request is checked against your Statisfy role at that moment, so Claude can do through MCP what your role lets you do in the app, and no more. For what each role does in the app, see User management and roles.

What each role can do

The table shows what each role can do on a connection allowed to make changes. On a read-only connection, every role reads only.
  • Member sees only their own accounts. Claude reads and changes only the records in their book. Admin, Builder, Member All Accounts, and Viewer see every account.
  • Viewer is read only. Claude can’t make changes for a Viewer, even on a connection with Make changes ticked.
  • Meetings follow the app. Admins find every meeting; everyone else finds the meetings they see in the app.
  • Some actions are for admins only: deleting accounts, opportunities, projects, and custom object records; changing workspace setup; publishing a campaign or a skill; enabling an Agent Studio automation; activating a digital worker; sharing a clip; and reading the audit log. A builder can draft a campaign, for example, but only an admin can publish it.
  • A role change applies within a few minutes. No one needs to reconnect. If someone leaves the workspace, their connections stop working.
When a request isn’t allowed, Claude tells you why. For example: “This connection can only read. Reconnect Statisfy with write access to change data.”

Your workspace’s products

Claude reaches only the parts of Statisfy your workspace has, as in the app. For example, opportunities, portals, and digital workers are available only when your workspace has the product that includes them. If your workspace has no active plan, Claude tells you so.