A tenant-wide setting that hides personal teams across the organization. When it is enabled, every user works exclusively from shared teams: personal teams disappear from team pickers and URLs, stories in personal teams stop executing, and new users are provisioned onto a shared team instead.
Nothing is deleted. Personal teams and their contents remain in the tenant. The setting is fully reversible.
ℹ️Info
Personal teams in Tines
Each Tines user has a personal team by default. Personal teams are useful for experimentation, but some organizations need all automation to live on shared, role-controlled teams that tenant owners can govern and audit.
Disable personal teams addresses that need for governance without removing data or migrating content.
What changes when personal teams are disabled
With the setting enabled:
Personal teams are hidden from team pickers, the team list, sharing dropdowns, and navigation.
Personal-team URLs (for example
/personal/...) redirect to one of the user's shared teams (most recently visited / first joined as fallback).Stories owned by personal teams cannot execute. Webhooks return HTTP
422. Send to Story actions fail with a clear error in the run log. New events cannot be created for those stories.The Convert to story action in Workbench is hidden.
The Team and personal team access option is removed from sharing dropdowns. Existing sharing rows display as Team access only.
The guided onboarding tour is skipped for new users. The onboarding form and helper panel still run.
The Personal team AI actions toggle is hidden in AI settings.
New users are added to a shared team through admin invite, JIT, REST, or SCIM. Users who cannot be placed on at least one shared team are rejected with a structured error. (see New user provisioning)
Only tenant owners can enable or disable this setting.
Disabling personal teams
Navigate to Users (
/settings/users).Turn on the Disable personal teams toggle.
Review the dependency scan in the confirmation dialog (see below).
Resolve any blockers, choose how to handle Send to Story callers if needed, and confirm.
Both enabling and disabling the setting are recorded in the audit log.
ℹ️Info
Dependency scan
Before personal teams are disabled, Tines scans the tenant and surfaces three areas of impact.
Records shared from personal teams
Counts of shared credentials, resources, and templates that live in personal teams but are referenced elsewhere in the tenant. These objects keep working after personal teams are disabled. Only tenant owners can edit them once personal teams are hidden.
Users without a shared team
Users who belong only to a personal team. Personal teams cannot be disabled while any non-service-account user is in this state.
Add each listed user to at least one shared team from their user settings page before trying again. Open the list from View in the dialog.
Send to Story into personal teams
Shared-team stories that call a story in a personal team through Send to Story. If these callers are left enabled, they fail once personal teams are disabled.
When callers exist, choose one of:
Disable caller stories - Tines disables each calling story when personal teams are turned off. Stories can be re-enabled later from the story page.
Allow caller stories to fail - Calling stories stay enabled. The next time one runs, the Send to Story action fails with a structured error.
Open the caller list from View in the dialog. Each row links to the calling story.
SCIM landing team
If SCIM user provisioning is enabled, the confirmation dialog requires a SCIM landing team and role.
❗️Important
Personal and archived teams are not available as landing teams.
The same SCIM landing team and role can be reviewed or updated later under Settings → Authentication → User provisioning while personal teams remain disabled.
New user provisioning
While personal teams are disabled, every provisioning path must place the new user on at least one shared team:
Admin invite / bulk invite: Invite must include at least one shared team.
REST
POST /api/v1/admin/users: Request must include a shared-team membership.JIT first login: User must map to at least one shared team through group sync.
SCIM: User is placed on the SCIM landing team until group memberships arrive.
If provisioning would leave a user with only a personal team, the request is rejected with a structured error.
Learn more in User provisioning and JIT.