One boundary to the data
The backend is the only component that touches the database or an external API. The browser client and the local MCP server both reach it the same way — over the REST API, authenticated and scoped. There is no second door.
Permissions in two layers
Every request passes a route-level gate and then row-level scoping. The company ceiling is checked before role, so a module switched off for the company cannot be reopened from inside it. The HTTP layer and the agent tools call the same permission implementation, so the two cannot drift apart.
Scoped access tokens
- Personal access tokens authenticate as the real user but are hard-scoped at the routing chokepoint.
- A token reaches Tasks and read-only Projects — nothing else, checked before the user is even resolved.
- A token cannot mint more tokens, because that path is not in its allowlist.
Connections
Calendar, mail, and Slack connections use OAuth and store refresh tokens, not passwords. Gmail access is read-only. You can disconnect any integration at any time, which revokes the stored token.
Reporting an issue
Security reports can be sent to security@example.com. This page is placeholder copy for a demonstration site and does not describe a production system.