Tenant-wide control over personal teams access

Admin, Enterprise, Teams |

Tenant owners can now hide personal teams across an entire organization, so every story lives on team-owned, role-controlled surfaces. It's built for compliance-focused enterprises that need shared, governed ownership of every story.

When Disable personal teams is on, everyone works exclusively from shared teams. Personal teams disappear from team pickers, sharing dropdowns, and URLs. Stories owned by personal teams stop running, so webhooks return a 422 and Send to Story actions fail with a clear reason. New users are provisioned onto a shared team. Nothing is deleted, and the setting is fully reversible.

To turn it on, a tenant owner opens Settings → Users and toggles Disable personal teams. Tines runs a dependency scan first, surfacing anything that needs attention before you confirm:

  • Send to Story callers that target personal-team stories

  • Shared credentials and resources owned by personal teams

  • Users who only belong to a personal team

You resolve blockers inline by bulk-disabling callers or allowing failures. SCIM-enabled tenants also pick a landing team for newly provisioned users. Every enable and disable is written to the audit log.

Available to enterprise tenants. Reach out to your account contact to turn it on.

Learn more in the docs

Seth Cohen

Built by you,
powered by Tines

Already have an account? Log in.