Security and data
What Stevin can and cannot reach, the checks before data is changed, what is recorded, and the controls admins have.
What Stevin can reach#
Stevin does not have unlimited access. What it can reach is decided by three things together:
- What is connected. It can reach only systems that are connected and authorized under Integrations or MCP servers.
- What is reviewed. Every tool of an MCP server must be allowed by an admin. Stevin does not use tools that have not been allowed, and a tool that changes comes back for review.
- Who is asking. When acting for a person, it is bound by that person's role and permissions.
In chat tools, it sees only the channels or groups it has been added to and the direct messages sent to it.
Each workspace is separate#
Each team has its own workspace. Its data, integrations, skills and settings belong to that workspace only.
Checks before data is changed#
| Kind of action | Rule |
|---|---|
| Read | Runs directly once the tool is allowed |
| Write | Asks a person first by default; admins can adjust this per tool |
| Delete and irreversible | Always asks a person; cannot be made automatic |
See Approvals.
Code execution#
Programs Stevin writes run in a sandbox with no network access. Installing a package into the sandbox needs approval unless an admin has listed it. See Code execution.
Credentials#
App credentials and secrets you enter in the console are stored on the server and are not shown again after saving. Webhook keys can be rotated at any time.
What is recorded#
- Every task's goal, status and result are in Activity.
- Approval requests and their outcome are part of the task they belong to.
- Every permission change is listed under Recent changes on the Permissions page, with who made it and the previous value.
- Skill revisions are kept.
Controls available to admins#
| What you want to control | What to use |
|---|---|
| Which systems Stevin can reach | Connect and disconnect integrations and MCP servers |
| Which actions it can use there | Tool review on each MCP server |
| Which actions must be asked about first | Asks first or Runs directly per tool, and the conversation settings on the Permissions page |
| Who can configure all this | Roles and permissions |
| Who can see whose tasks, records and transcripts | Data scopes on the Permissions page |
| Which tools an automation can use | The automation's MCP server selection |
| Who can sign in | Invitations, sign-in methods, and disabling accounts on the People page |
Calls and recordings#
Live sessions and phone calls are recorded and transcribed, and kept in the library. Phone calls are accepted only from numbers that members have linked and verified. Where the law in your region requires it, tell other participants that a conversation is being recorded.
Reporting a security issue#
If you find a security issue, write to support@stevinhq.com. Do not include passwords or keys in the message.