Manage Teams from Settings
Use the team administration routes when the goal is to create or maintain team structure rather than simply browse teams.
Team settings are the administrative counterpart to the main team pages.
- Open the right team administration route.
- Manage team structure safely.
- Keep team browsing and team administration separate.
Where this happens
Do the work
- 1. Open `/workspace/settings/teams` when you need to create or manage team structure.
- 2. Choose the target team if the change applies to an existing team.
- 3. Open the team-members route when the real change is who belongs to the team.
- 4. Save the change and then verify the visible team surfaces reflect the new structure.
Keep this clear
- Ignore the legacy typo alias route when sharing links; the canonical team-members route is the stable one.
Keep Going in Settings and Configuration
Stay in the same interface and move to the next closest task in this topic when needed.
Update Your Profile Settings
Use the profile settings page for personal account-level changes that belong to you rather than the whole workspace.
Update Your Preferences
Use preferences for appearance or personal UX settings that change how the product feels, not what the workspace stores globally.
Update Workspace Settings
Use the workspace settings page for workspace-wide metadata and identity changes.
Manage Workspace Members
Use the member administration route for invitations and access changes rather than the read-only member directory.
Manage Task Labels
Use the task label settings route when the shared task vocabulary itself needs to change.
Manage Project Labels
Use the project label settings route when the shared project label catalog needs a workspace-wide change.
Manage Task Templates
Use the task template routes when a repeatable task shape should be captured as reusable configuration.
Manage Project Templates
Use the project template routes when a repeatable project structure should become reusable configuration.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.