Permissions, security and APIs for all apps
Each organisation gets its own subdomain with strict tenant separation. You decide who may do what – down to individual actions. Your data is stored in Zurich.
Platform
- Permissions down to individual actions
- Roles and permissions apply across all apps and go down to individual actions.
- Secure sign-in
- Two-factor with one-time codes (TOTP) and backup codes, plus passkeys. Sign-ins and changes are logged, showing old and new values.
- Data in Switzerland
- Database and files are stored in Zurich, and email sending runs through the same region. Data export per person, deletion requests and consent management are built in.
- Open, but controlled
- Public REST API with scopes and rate limiting, outgoing webhooks and Claude access that is never allowed more than the person behind it.
Example
Settings · Muster AG
Role “Accounting”
create invoice: yes · delete: no
Anna Muster
passkey and two-factor active
API access “Website”
scope: read contacts
Webhook “Invoice paid”
active
Claude · “Create 5 contacts”
awaiting approval
What is in the folder
Organisation and permissions
- Your own subdomain per organisation
- Strict tenant separation
- Roles and permissions down to individual actions
- Sign-in log and change log (old → new)
Security and data protection
- Two-factor sign-in (TOTP) with backup codes
- Passkeys
- Data stored in Zurich: database, files, email sending
- Data export per person as JSON, PDF or ZIP
- Deletion requests and consent
AI and Claude
- AI with a monthly budget and hard stop
- Consent per AI provider
- Claude access (MCP) in CRM, Aufgaben, Kampagnen, Termine, Ticketing, Gastro, E-Commerce and Sites
- Never more permissions than the person whose key Claude uses – checked on every call
- Write actions can wait for approval and are logged
APIs
- Public REST API with scopes
- Rate limiting
- Outgoing webhooks, e.g. contact created, invoice paid, task completed
Works together with
- CRMRoles and permissions also apply in the CRM, and the “Contact created” webhook passes on new entries.Roles and permissions also apply in the CRM, and the “Contact created” webhook passes on new entries.
- AufgabenClaude can create and edit tasks – within the permissions of the person whose key it uses.Claude can create and edit tasks – within the permissions of the person whose key it uses.
- FinanzenThe “Invoice paid” webhook reports incoming payments to your other systems.The “Invoice paid” webhook reports incoming payments to your other systems.
Frequently asked questions
Database and files are stored in Zurich, and email sending runs through the same region. Each organisation has its own subdomain and is strictly separated from other organisations.
See who may do what in your organisation
In a demo, we show you roles, sign-in, APIs and Claude access using a sample organisation.