Skip to main content
Snaga
Start

Security

Your work. Your control.

Choose which company resources agents can access, which actions need approval and how much work may cost. The sections below explain how these controls work and where to configure them.

Company OSExample workflow
Your rules
Your agents work as a team

A reminder that you set the boundaries.

Work under your control
The Плямки of Snaga · Poseidonka

  • Important actions wait for you

    You decide what an agent does on its own and what it asks about first: everything, only the risky things, or nothing. Before such an action the run stops and waits for your answer — allow it, decline with a reason, or refuse. If nobody answers within a day, the action does not happen.

    How approvals work

  • The Chief of Staff only proposes

    Adding an agent, changing a schedule, the rules or a budget — the Chief of Staff can only suggest it. The change waits until a person applies or rejects it, and a proposal nobody answers expires after 7 days.

    How Snaga works

  • Separate company workspaces

    Agents, conversations, runs, files, keys and the bill belong to one company, and nothing crosses into another. A person can belong to several companies, but an API key works only in the company that created it.

    Companies and members

  • Keys with limited rights

    Every API key carries a set of permissions — for example, read agents and start work, nothing more. Billing access is not included unless you choose it. The full key is shown exactly once, when you create it.

    Authentication

  • Pause agent work

    A company can be paused: every automated run — schedules and missions — stops, while your own chat with an agent still answers. For an emergency, the company's founder can switch on safe mode, which halts all non-essential agent work.

    Rules and safe mode

  • Every decision is on record

    A run keeps every approval: who decided, when, and what — and the reason for a refusal. Changes to your company's rules are appended to a ledger whose integrity can be checked.

    Runs

  • Connections only for the agents you choose

    You connect the services you already use and decide which agents may use each one. Stored secrets are never sent back through the API — you only ever see them masked.

    Integrations

  • Signed notifications

    Snaga signs event notifications with a shared secret. Your server can verify the signature to check the source and integrity of each notification.

    Webhooks

Availability and limitations

Snaga does not currently hold a SOC 2 report or ISO 27001 certification, and a penetration-test report is not available. Contact us if you need security documentation for your organization.

Read how we handle and protect your data: Data Processing Agreement, the Privacy Policy and the Acceptable Use Policy.

To report a security issue, use our contact and select Security.