# Scan: Spinnable AI employees > GAMMA-Ray v0.0.155 (beta, for review; every rating is experimental). An example GAMMA-Ray beta rating of Spinnable AI employees: freedom 4, 4, 4 across its configurations; deployment governance not assessed. > Page: https://gamma-ray.sgit.ai/scans/spinnable-ai-employees/ · Source: data/scans/spinnable-ai-employees.json Example · beta rating · a product as its vendor documents it · read 2026-11-10 · not seen by the vendor Role-based AI workers with their own email address, memory, scheduled tasks and access to 35+ connected tools, reachable by email, WhatsApp, Slack, meetings and voice. A scan of a product as its vendor documents it, not of any one deployment. Made by the report studio: a researcher-assessor, a challenger, then the scorer. Part of the first Portuguese cohort. Built only from Spinnable's own public pages (product, documentation, blog, customer stories, legal and security pages). Nothing was tested. If you are the vendor and something here is wrong, the correction will be made and dated. *Figure. The label for this rating; its contents are in the text.* 4 Freedom as shipped Acts widely 4 Freedom at most Acts widely 15 Controls it brings as shipped n/a Deployment governance not assessed ## How to read it This is a product, not a deployment. A product has no owner, no policy in force and no mandate until somebody runs it, so it is given **no governance level and no level held**: those belong to a deployment. What a product has is a freedom level for each way it can be configured, and a list of the controls each configuration brings. *Figure. The freedom level of each configuration; the table has the same.* | Configuration | What changes | Freedom | Controls | Turned on by the operator | |---|---|---|---|---| | **As shipped** | Spinnable AI employees (called AI workers in the documentation) with its documented defaults. | 4 Acts widely | 15 | nothing | | **Multi worker** | Two or more workers in the same team or workspace, so one can delegate tasks to another. | 4 Acts widely | 15 | several agents coordinate inside the organisation | | **Read only connection** | A tool connection set to Read: workers using it can search and look up but not create, change or send. | 4 Acts widely | 16 | it asks for narrower access than the whole account | The same product is a different agent in each row. A rating of a deployment starts by saying which row it is. An indicator with no evidence is reported as not evidenced; it is never read as a no. ## The profile *Figure. One square per indicator, by question; every answer is listed below.* ## The grant: what it can actually do The questions measure what is said about an agent: its purpose, its rules, its controls. The grant is the other half: what its permissions let it do, capability by capability, and what stands in the way of each. This is RiskMandate's measurement, and it depends on the permissions a deployment was given. **Not measured.** Not measured. No deployment shape for this product is published in the capability grammar. ## Seen, and not credited - AI disclosure when the default email signature is off The corporate-email page, a captured source, says the disclosure footer is part of the Spinnable signature card and is not controlled separately. It says that turning off Email signature removes the footer, and its troubleshooting gives that as the fix when the footer appears on outgoing emails. No other disclosure is documented, so I56 is credited for the default only. [Source](https://docs.spinnable.ai/guides/corporate-email) - A configured approval step for worker actions The home page says actions with external consequences need approval, but no captured documentation page describes an approval setting. The corporate-email page's troubleshooting says to 'Designate a single point of contact for send approvals and critical instructions' and to make this explicit in the Worker Policy, which is a prose rule and not a mechanism. Not credited as I38; I17 rests on the home page statement only. [Source](https://docs.spinnable.ai/guides/corporate-email) ## What its evidence reaches *Figure. The mashup graph with this agent's evidenced indicators lit.* ## Every answer, with its source ### What is the agent built on? - *Not evidenced.* It is a vendor's assistant, used as supplied. - *Not evidenced.* It runs on an AI platform with the organisation's own data, without executing arbitrary code. - *Not evidenced.* It is configured on a low-code or no-code builder and acts on real organisational data. - **As shipped.** It generates and executes code with local or cloud privileges. Workers run Python code and custom scripts in a sandbox, where stored credentials are exposed as environment variables. [Source](https://docs.spinnable.ai/guides/worker-vault) (documented) - *Not evidenced.* It is built in-house: the organisation controls its identity, tools and boundaries. ### Does it act, or only answer and recommend? - *Not evidenced.* It follows fixed rules, with no reasoning. - *Not evidenced.* It retrieves information and recommends actions; a person acts. - **As shipped.** It executes actions itself. The documentation states workers act in connected tools, such as updating databases and sending emails. [Source](https://docs.spinnable.ai/concepts/ai-workers) (documented) - **As shipped.** It is in production: a public source names a customer or gives usage figures for what it does on its own. The home page quotes Smart Role's CEO: one worker manages his calendar, runs his outreach and keeps his pipeline current. A testimonial; no usage figures for what the workers do. [Source](https://www.spinnable.ai/) (documented) ### How far does it reach? - *Not evidenced.* It works in one domain's data. - **As shipped.** It works across several domains or systems. Workers connect to many tools across a business, from email and calendar to GitHub, Notion and Salesforce. [Source](https://docs.spinnable.ai/tools/overview) (documented) - **As shipped.** It connects to external tools or services across a trust boundary. Each tool is connected by authenticating with the outside service through OAuth or an API key. [Source](https://docs.spinnable.ai/tools/overview) (documented) ### Does it work with other agents? - **Available, if the operator turns it on.** Several agents coordinate inside the organisation. With two or more workers in a team, a worker can delegate tasks to the others; each sub-task shows as its own block in the activity trail (release notes, 10 June 2026). [Source](https://docs.spinnable.ai/release-notes/2026-06-10) (documented) - *Not evidenced.* Agents operate across organisational boundaries or disparate stacks. - *Not evidenced.* There is a published protocol or communication layer between agents. - *Not evidenced.* Others build on it: third parties publish integrations, skills or agents for it. - *Not evidenced.* It exposes an agent interface: a published MCP server, an agent card, or an API documented for agents to call. ### What is the person's role? - *Not evidenced.* The person operates: every action is prompted and controlled by them. - *Not evidenced.* The agent suggests; the person reviews and approves each action. - **As shipped.** The agent handles routine tasks; the person is consulted on exceptions. The home page FAQ states that a worker schedules tasks, sends follow-ups and completes workflows without being prompted each time, that it will not take actions with external consequences without the person's approval and asks when unsure; no documentation page describes how that approval is configured. [Source](https://www.spinnable.ai/) (documented) - *Not evidenced.* The agent works independently; the person approves critical decisions only. - *Not evidenced.* The agent has full autonomy within boundaries; the person monitors. ### Is what it is for written down? - **As shipped.** Its purpose and permitted tasks are stated in writing. The documentation states what the workers are for: joining a team and doing its work, by role or for a specific process. [Source](https://docs.spinnable.ai/introduction) (documented) - **As shipped.** Its autonomy limits and the tools it may use are defined. Tools must be granted to each worker separately, with a chosen connection and capabilities such as read or send. [Source](https://docs.spinnable.ai/concepts/tool-permissions) (documented) - **As shipped.** Its limits and known failure cases are documented for those who use it. The troubleshooting page documents failure cases, such as a worker stopping mid-workflow, with causes and fixes. [Source](https://docs.spinnable.ai/troubleshooting/index) (documented) ### Does it have its own identity and only the access it needs? - *Not evidenced.* What it can reach is enumerated: scopes, permissions, tools. - *Not evidenced.* Its authorisation is published as metadata that anyone can read. - **Available, if the operator turns it on.** It asks for narrower access than the whole account. A tool connection can be set to Read, so the workers using it can look things up but not create, change or send; Read is preselected for a new connection, while Full access remains the default and is needed to act. [Source](https://docs.spinnable.ai/release-notes/2026-08-05) (documented) - **As shipped.** It has its own identity, separate from any person's. Each worker has its own email address, separate from the people it works for. [Source](https://docs.spinnable.ai/concepts/ai-workers) (documented) - *Not evidenced.* Its identity is cryptographic and can be checked by others. - *Not evidenced.* Its tokens are bound to the service they were issued for and are not passed on. ### Is it in a registry, with an owner? - *Not evidenced.* The organisation keeps a registry of its agents. - **As shipped.** Each agent has a named owner. Each worker has a manager who administers its settings; the role can be handed to another user. [Source](https://docs.spinnable.ai/guides/change-manager) (documented) - *Not evidenced.* Agents are retired by a defined process. ### Who is accountable for it? - *Not evidenced.* A named executive or body is accountable for the organisation's agents. - *Not evidenced.* Roles and responsibilities for AI risk are documented. ### Is there a policy that governs it? - *Not evidenced.* A governance policy for agents is published. - *Not evidenced.* Agents and use cases are classed by risk. - *Not evidenced.* The laws that apply to it are identified. - *Not evidenced.* New agents pass an approval or review before they run. ### Can a person step in or stop it? - *Not evidenced.* High-impact actions need a person's approval. - **As shipped.** There is a way to pause or stop it. A person can interrupt a worker from the chat with Send now, which cancels the reply it is generating; the page describes stopping a run, not stopping the worker as a whole. [Source](https://docs.spinnable.ai/concepts/communication-channels) (documented) - **As shipped.** There is a defined escalation path. A recurring task that fails three runs in a row is paused and the worker's manager is emailed with the reason. [Source](https://docs.spinnable.ai/release-notes/2026-10-28) (documented) ### Is what it does logged? - **Claimed, not counted.** Its actions are logged. The documentation states every tool action is logged with time, worker, tool, method and outcome; documented, not observed. [Source](https://docs.spinnable.ai/guides/connecting-tools) (documented; this fact has to be observed or measured to count) - *Not evidenced.* The log is tamper-evident and kept for a stated time. ### Is it watched while it runs? - *Not evidenced.* It is monitored in operation. - *Not evidenced.* Anomalies are detected in real time and raise alerts. ### What stands between it and what it should not do? - *Not evidenced.* A limit on it is enforced by something outside its own reach. - **As shipped.** A limit on it is a setting that its own account could change. Who may message a worker is a per-worker setting in the same workspace account that runs the worker, changed by its manager or co-managers; the page does not say the worker itself can change it. [Source](https://docs.spinnable.ai/guides/worker-communication-restrictions) (documented) - **As shipped.** A limit on it is a rule in prose. Persistent rules for a worker are written in prose in its Worker Policy. [Source](https://docs.spinnable.ai/guides/corporate-email) (documented) - *Not evidenced.* Policy is enforced as machine-readable rules. - *Not evidenced.* The difference between what it can reach and what it is for is stated. ### Is it tested, and are the results shown? - *Not evidenced.* Test or evaluation results are published. - *Not evidenced.* It is tested for safety and security, including by attack. - *Not evidenced.* People who did not build it take part in assessing it. ### What happens when it goes wrong? - *Not evidenced.* There is an incident process for agents. - *Not evidenced.* Incidents and errors are communicated to those affected. - *Not evidenced.* There is a plan for a failure of a third party it depends on. ### Do people know it is an AI, and can they answer back? - **As shipped.** It tells the people it talks to that it is an AI. By default, a worker's outbound email carries a signature footer saying it is an AI worker hired through Spinnable; a manager can switch the signature off, which removes the footer. Email only; no disclosure is documented for WhatsApp, Slack or voice. [Source](https://docs.spinnable.ai/guides/corporate-email) (documented) - **As shipped.** There is a channel to report problems with it or contest its output. A support page gives an email channel for reporting problems with a worker, for managers and for workers themselves. [Source](https://docs.spinnable.ai/support/contact) (documented) - **As shipped.** It is machine-readable for agents: it publishes an llms.txt, an AGENTS.md, an API description or an agent card. An llms.txt resolves on the marketing site and on docs.spinnable.ai, fetched on 10 November 2026. [Source](https://www.spinnable.ai/llms.txt) (observed) ### What data does it use, and under what rules? - **As shipped.** The data it uses is described. The privacy policy lists what the agents access: email, calendar, documents, messages and data from connected platforms. [Source](https://www.spinnable.ai/privacy-policy) (documented) - *Not evidenced.* There are data quality rules for what it reads. - *Not evidenced.* Its privacy risk has been examined. ### What does it depend on from others? - *Not evidenced.* The models and third-party components it uses are listed. - *Not evidenced.* Third-party components are monitored and have risk controls. ### Has anyone independent checked? - *Not evidenced.* A public certificate or audit report covers it. - *Not evidenced.* Compliance evidence is produced continuously, ready for a regulator. ### Is the organisation behind it ready? - *Not evidenced.* There is a stated strategy for agents. - *Not evidenced.* The people who work with it are trained. - *Not evidenced.* Its value is measured. - **As shipped.** It is improved on a regular cycle. The documentation index lists dated release notes from 8 January to 28 October 2026, most weeks, with some gaps. [Source](https://docs.spinnable.ai/llms.txt) (documented) - *Not evidenced.* The organisation's risk management covers agents. ## The vault This rating, its evidence list, its grant and the questions it was made against are kept in a public sgit vault (`kghdiwq3`, published 2026-11-10). Anyone can read it with this key: `sgit_public_read_76f8699d4556bfb03360cbda6e61d0c7f76b07e13444704e4ced072a90a1742c:kghdiwq3` With [sgit](https://sgit.ai/): `sgit clone sgit_public_read_76f8699d4556bfb03360cbda6e61d0c7f76b07e13444704e4ced072a90a1742c:kghdiwq3`. The key reads; it cannot write. An operator who wants to add what only they hold forks the vault into a private one.