Security

Authentication, permissions, approval, auditing, and revoking access for the MCP connection.

Authentication

Solk MCP works only with OAuth 2.1 (or with an API key created by an admin). Your password is never given to the assistant or the client: the client redirects you to your Solk installation's own sign-in and consent pages, and once you grant access, it receives a short-lived access token.

Access token 1 hour
Refresh token 60 days; rotated on every refresh
PKCE Required (S256)
Redirect URIs https:// and loopback only
Token storage The server stores only a SHA-256 hash

Permissions

The assistant works under your account:

  • Your role (admin / sales), your module permissions, and record visibility all apply as is. If you connected as a sales rep, the assistant sees only what you can see.
  • Email content is returned according to the mailbox owner's sharing settings; the text of messages you aren't allowed to see is never given to the assistant.
  • Scopes are separate: if you grant only crm.read, the assistant can't change any records.
  • Deleting and merging only with the separate Permanent delete (crm.delete) permission: an unticked box on the consent screen; never granted to personal API keys. Every delete tool requires confirm: true; companies aren't deleted, they're made passive. Without this permission no tool deletes records (remove_relation only removes a relationship link). Delete tools

Approval

Claude asks for permission the first time it uses a tool. Because read tools are marked "read-only", you can grant them permanent permission; for write tools, we recommend having Claude ask for approval on every call. Organization owners can restrict which tools are available in Claude's admin settings.

Auditing

  • Every tool call is recorded in the Solk audit log with the user, the tool name, and the connected app's name.
  • Records created by write tools appear with their owner and timestamp, just as if they had been created in the web app; the same events are sent to integrations (Slack, webhooks…).
  • Settings → App connections (Ayarlar → Uygulama bağlantıları) shows each app's connection date, last use, and operation count.

Workspace rule (admin)

Admins see two switches in the Workspace rule card under Settings → App connections (Ayarlar → Uygulama bağlantıları):

Switch Effect
Allow AI app connections When off, /mcp returns 403 to connected clients — clients like Claude or ChatGPT can't connect and existing connections stop. The REST API and the mobile app aren't affected.
Read-only When on, connected apps can read records, run reports and read canvases; write tools aren't listed and calling one returns a "read-only rule is on" error.

Every change is written to the audit log. Turning the rule back on lets connections work again (tokens aren't revoked).

Revoking access

Who How
User Settings → App connections → Remove access (Ayarlar → Uygulama bağlantıları → Erişimi kaldır) — all of that app's tokens are revoked immediately.
Admin Deactivating the user cuts off all of their connections; the workspace rule stops everyone's connections.
On the Claude side Remove the connector from the Connectors list, or click Disconnect.

Data processing

The MCP server runs inside your installation. With the single address (https://mcp.solk.app/mcp), Solk's gateway only routes requests to your workspace — it stores no passwords, authorization codes, tokens or record data, and adds your workspace's name to the tokens it passes on so it can route them. Data the assistant reads is sent to the AI service you use (for example, Anthropic) under that service's terms. Decide which users can connect based on your organization's AI usage policy.