Connected without giving up control

Google, cleanly separated

Signing in with Google and access to Calendar, Drive and Gmail are two separate grants, each with its own lifetime. You link your account in one extra click, so your login never quietly gains the right to read your mail. The OAuth credentials live per organisation under Instellingen → Google, and refresh tokens sit encrypted in the vault.

Calendar, Drive and Gmail at the client

Approved leave shows up in Google Calendar, and a project's Drive panel opens straight into the client's folder on the Shared Drive. Matched emails land on the timeline as touchpoints, but stay pending until the mailbox owner approves them. Drive stays the source of truth: schakl. links and shows your files, it doesn't keep a second copy.

• Calendar: approved leave one-way to Google, synced incrementally
• Drive: browse and attach to a client or project, a new client folder from a template
• Gmail: only mail from known contacts, metadata first, the body only after approval

Your API is an AI surface by default

The whole API runs as an MCP server at /mcp: every endpoint becomes a tool for Claude Code or any other AI client, generated from the OpenAPI spec. Each call goes in-process through the same gate as the web app (hostname to organisation, RLS, permissions), so an AI can never reach past your tenant or beyond the key's scopes. You mint API keys per person or as a service account and choose exactly which permissions travel with them.

• Keys are tenant-scoped, revocable and optionally non-expiring
• Read-first is a choice at mint time: a cautious key only reads
• Connect in one line: claude mcp add with your Bearer key

An assistant that proposes, you decide

The built-in assistant runs on the AI provider you choose (Anthropic, OpenAI or a compatible endpoint), with your own key encrypted per organisation. It lives in the page where the work already happens, not on a separate chat island, and answers with its sources as clickable record chips. Nothing is saved until you hit apply, and every tool call stays inside your role and tenant. With no provider configured, there's no AI button to be seen anywhere.

• Writing assist in the editor, faster time entry and reconstructing a whole day
• Numbers come from the services, the model only writes the prose
• A client digest and a drafted monthly report, always as a proposal first

Open, documented, connectable

Everything runs on one API with an automatically typed client, so there's no back door around the database. On top of it come a documented public API, webhooks and an n8n connector for your own automations, plus scheduled PDF reports that go out on their own under your brand. The foundation is here today: every new module extends that same API and the same toolset.