> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/create-and-manage-teams.md). # Create and manage teams Teams group the people who share OKRs: departments, functions or project groups. Rhythms Admins create teams at **Settings › Workspace › Teams**; Team Owners add members and create sub-teams from the same list. OKRs assigned to a team are listed under that team in the left navigation, and the Team tab of Settings › OKRs › Permissions decides who can create, edit and manage them. ## Open the Teams page Click **Settings** in the left navigation, then **Workspace › Teams**. The page has an **Active** and an **Archived** tab, a **Search teams** box and a **Create Team** button. Each row shows the team's Name (with an arrow to expand its sub-teams), Team Members count and Owners. The three dots at the end of a row open the actions menu: **Edit**, **Manage members**, **Add sub teams**, **Archive** and **Delete** (archived teams show **Unarchive** instead). Team Owners see Manage members, Add sub teams, Archive and Delete only for teams they own. ## Create a team Only Rhythms Admins can create a top-level team. 1. On the Teams page, click **Create Team**. 2. Enter the **Team name**. 3. Pick one or more **Team owner**s. At least one owner is required; adding a second owner means the team is not dependent on one person. 4. Optionally **Add description**. 5. Leave **Parent team** empty for a top-level team, or select a team to create the new team under it. 6. Click **Create Team**. ## Create a sub-team Rhythms Admins, and Team Owners of the parent team (or of any team above it), can create sub-teams. On the Teams page, click the three dots on the parent team's row and choose **Add sub teams**. The same form opens with **Parent team** already set; fill in the name and owners and click **Create Team**. The new team appears nested under its parent. Sub-teams do not inherit anything from the parent team. Membership, owners and check-in settings are set on each team separately, and OKR permissions are workspace-wide rather than per team. Owners of a parent team can, however, manage its sub-teams: they can add members, edit, archive and create further sub-teams under them. ## Add and remove members, and set Team Owners Rhythms Admins and the team's owners (including owners of a parent team) manage membership. 1. On the Teams page, click the three dots on the team's row and choose **Manage members**. The members page opens with the breadcrumb Teams › {team} › Manage Members. 2. Click **Add members**, then tick the people to add. Any active user can be added, including Guests. New members join as Team Member. 3. To make someone a Team Owner, use the dropdown in the **Role** column and switch **Team Member** to **Team Owner**. Switch it back to demote them. 4. To remove someone, click the three dots on their row and choose **Remove**. Removing yourself is labelled **Leave Team**. ![The Manage Members page for a team, with the Add members popover listing users to tick](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-42885dea5513970f7f27d5f973e519799e543819%2F24a85c2d-895c-4bec-aff0-435c4c461527-image.png?alt=media) Guests can be team members so that they see the team's OKRs, but do not make a Guest a Team Owner: Guests cannot perform any team-management action. The **Export** button on the members page downloads the member list as a CSV. ## Edit, archive, unarchive or delete a team * **Edit** opens the team's page where you can change the name, description, owners and parent team. * **Archive** opens an archive page that lists the team's current and future OKRs and its active sub-teams. Choose whether to reassign those OKRs to another team or unassign them, and where any active sub-teams should go; a team cannot be archived while it still has active sub-teams. Archived teams move to the **Archived** tab and keep their history. * **Unarchive** (on the Archived tab) makes a team active again. Its parent team must be active first. * **Delete** is available only for a team that has no OKRs and no sub-teams; otherwise the menu shows "Teams with OKRs or sub teams cannot be deleted" and you should archive instead. Deleting removes the team permanently. ## Team OKRs and permissions Assign an OKR to one or more teams when you create or edit it. Team members find their team's OKRs under **Your teams** in the left navigation (collapsed by default). Who can create, edit, manage and approve team OKRs is set on the **Team** tab at Settings › OKRs › Permissions: by default Team Owners can create OKRs for their teams ("OKR team owners"), while editing and managing an OKR is limited to its owners and their managers. See [OKR roles and permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md). ## Teams and directory sync Directory sync (SCIM) creates and deactivates users; it does not create teams or map identity-provider groups to teams. The only group Rhythms reads is the guest group, which assigns the Guest license. Add people to teams on the Manage members page, or through the Rhythms REST API. See [Set up automated user provisioning (SCIM) and HRIS integration](/workspace-settings-and-administration/team-users-and-access/set-up-scim-user-provisioning.md). ## Frequently asked questions **Who can create teams?** Rhythms Admins create top-level teams. Team Owners can create sub-teams under the teams they own. **Can a team have more than one owner?** Yes. Add as many owners as you need; a second owner is a good safeguard. **Do sub-teams inherit settings from the parent?** No. Members, owners and check-in settings are separate per team, and OKR permissions apply to the whole workspace. **Can Guests join a team?** Yes, as team members, which lets them view the team's OKRs. Guests cannot own OKRs or manage the team. **Should I archive or delete a team?** Archive when the team has, or has had, OKRs or sub-teams; it keeps history and you decide where the OKRs go. Delete only removes empty teams. **Where do team members see the team's OKRs?** Under Your teams in the left navigation, and by filtering any OKR view by team. ## Related articles * [OKR roles and permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.md) * [Add and manage users](/workspace-settings-and-administration/team-users-and-access/add-and-manage-users.md) * [Guest users: read-only access](/workspace-settings-and-administration/team-users-and-access/guest-users-read-only-access.md) * [Filtering and grouping OKRs in views](/goals-and-okrs/monitoring-and-reports/filtering-and-grouping-okrs-in-views.md) * [Set up automated user provisioning (SCIM) and HRIS integration](/workspace-settings-and-administration/team-users-and-access/set-up-scim-user-provisioning.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/workspace-settings-and-administration/team-users-and-access/create-and-manage-teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.