Safe by Design:

AI in Your Back Office, Under Your Rules

An MCP access profile decides which tools a person or a token may use. Start new users small and widen access when your team is ready.

• MCP Viewer: reads records and campaign flows and searches the documentation. It changes nothing.
• MCP Analyst: adds read-only questions on your data warehouse.
• MCP Editor: adds creating and updating objects and running campaigns and flows.
• MCP Full access: all tools. MCP No Access switches MCP off for a user.
• Custom profiles allow exactly the tools and operations you pick, for example Editor without stopping campaigns. New users start with No Access.

Every create and update goes through the same validation as the back-office screens, and can run as a dry run first.

• A dry run shows what would change before anything is saved.
• Updates show a before-and-after view.
• Riskier operations, such as starting a campaign, ask you to confirm.
• Validation catches structural errors before anything is saved.

You can always see what an assistant did, and on whose behalf.

• Every tool call is logged under MCP, Usage, with filters for tool, object type and token.
• Changes made through Sign in with Smartico are recorded under the user's own name; changes made with a token, under a dedicated AI/API user.
• Deactivate any token at once from the Access tokens screen.