Workspace authentication
Sign in through the supported identity flow and keep work in the right workspace.
Shared context across your teams. Scoped tool access, human approvals, model choice, and security policies your organization can review before rollout.
Sign in through the supported identity flow and keep work in the right workspace.
By default, every change an agent makes in a connected app waits for your approval, on every plan.
Review the security policy for each system and provider's processing locations.
Connect the apps a workspace needs, with the permissions its people authorize.
Current retention and deletion rules are published in our legal and security documents.
Keep reusable instructions and knowledge inside the appropriate workspace.
Follow credits and activity in your workspace's usage view.
Read the Data Processing Agreement and request a countersigned copy.
Discuss access, support, and your rollout with the team before committing.
Choose from the models available to your workspace for each agent.
Change an agent's model without rebuilding the workflow or approval rules.
Use quick models for routine work and deeper models for complex analysis.
The same context and approval rules across marketing, operations, finance, engineering, sales, and leadership. Work in Spinrun workspace chat, Slack, or email. Microsoft Teams is coming soon.
Spinrun reads spend and engagement across your connected tools, then hands back a ranked list of what to cut, keep, and scale.
Three architectural choices that make the security conversation concrete.
Connected app credentials are sealed and resolved at the gateway. Agents call scoped tools without receiving the underlying keys.
By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app read, write and destructive rules at the gateway on Free and Pro.
Spinrun uses model providers under their business and API terms. Read the AI governance policy for providers, processing, and retention details.
Illustrative workflows with sample data. Your team supplies the context and reviews the result.
“Merged pull requests and product issues become a linked customer summary.”
“Orders, refunds, and payments become a brief with the exceptions attached.”
“Connected account records and sourced research become a short meeting brief.”
How it works
Choose a team, the people who need access, and one useful outcome.
Authorize the supported tools the workspace needs and review their access scopes.
Keep changes subject to approval and set per-app rules before expanding the rollout.
Capacity, rollout, and support are scoped with your team. Contact us for current Enterprise availability and a proposal that fits your requirements.
Walk through tool access, approvals, data processing, and model choice with the team. Scope the first workspace together.
We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.
Read the Cookie Policy