# Security and permissions

> What your agent can and cannot do, and how your organization keeps control.

## What Dakso enforces

These are checked by the server on every request. They do not depend on how the agent behaves.

- **Your agent acts as you.** It can do what your role allows in that organization, and nothing more.
- **It never sees your Dakso password.** You sign in on Dakso's own page; the agent only gets a connection that an administrator can revoke at any time.
- **Stored secrets stay stored.** The values of the secrets your organization keeps for its tools are never returned to the agent.
- **Deleting is confirmed by a person.** Deleting and other irreversible actions are not run by the agent: you get a link and confirm them in Dakso.
- **Large campaigns are confirmed by a person.** An agent can only launch small campaigns on its own; anything larger is confirmed in Dakso.
- **Everything is recorded.** Each change carries a short description of what the agent did and why, in your organization's activity log.

## What your agent is asked to do

Dakso tells the agent to ask you before sending messages, launching a campaign or spending credits. A well-behaved agent does. Treat it as you would a new teammate: review what it proposes before you say yes, and give it a role that matches the work.

Your agent also reads content written by other people: conversations, contacts, documents. Dakso tells it to treat that content as data, never as instructions. If an agent suddenly proposes something you did not ask for, stop and check.

## Check the address

The only Dakso server is `mcp.dakso.ai`. If a page, a message or an agent asks you to connect to Dakso at any other address, do not connect and do not sign in.

## Control for administrators

- An administrator sees every action in the activity log and can cut any connection at once.
- Add `?read_only=1` to the address of an API key connection and the agent can look but not change anything.

## API keys

API keys are only for your own system integrations, not for connecting an agent. The Dakso team enables them per organization on request, for a set period; once enabled, an administrator issues them. Treat a key like a password: keep it out of chats and shared files.
