Teams are where OKRs, check-ins, and collaboration live in OKRnest. Each organisation has a Teams directory and a dedicated workspace per team for OKRs, members, cycles, and settings.

Teams directory

Open Teams from the sidebar.

Tabs

• All teams: Every team in the organisation
• My teams: Teams you belong to

Search and table

Use Search teams... to filter by name. The table shows:

Column	Meaning
Team	Name; click to open the team workspace
Cycle	Current or relevant cycle label
Check-in	Check-in cadence summary
Members	Member count

Parent teams show a chevron to expand or collapse child teams. The hierarchy reflects parent team relationships (departments under divisions, squads under departments, etc.). A star icon marks teams you are a member of on All teams.

Creating a team

Click Create new team (desktop) or New team (mobile). Requires create team permission (Admins and Owners).

In the Create New Team sheet:

Field	Notes
OKR Team Name	Required
Parent Team	Optional; No parent team for a root team
Cycle Length	Required; choose a standard length (e.g. quarterly) or a custom template if your org defines one. Cycle length cannot be changed after creation.
Check-in Cadence	How often members should update key results (weekly, bi-weekly, monthly, or custom)
Team Members	Add existing users with Add Member, or Invite more users

Submit with Create Team.

Team workspace

Click a team name to open its workspace. The sidebar sections are:

Section	Purpose
OKRs	Create, update, and view status for the selected cycle period
Check-ins	List and run team check-ins
Actions	Team action board (when Actions is enabled)
Members	View and manage who belongs to the team
Activity	Chronological feed of changes on this team
OKR Cycles	List all cycles, archive, edit dates, delete
Settings	Team name, parent, cadence, delete team

Breadcrumbs show Teams → {team name} (and the section name when applicable).

OKRs section (Create, Update, Status)

Inside OKRs, use the period selector (Select period, previous/next arrows) to pick the cycle. Three tabs mirror the OKR workflow:

1. Create — Draft or edit objectives and key results
2. Update — Enter progress on key results
3. Status — Traffic-light summary for the whole team

Permissions gate each tab (for example edit OKRs, set OKR status, view status). See Creating OKRs and Updating Key Results for tab-specific help.

Leaving Create with unsaved edits prompts: You have unpublished changes in Edit. If you leave, your edits will disappear. Continue?

Members

The Members section lists everyone on the team. Admins and team editors can add or remove people. Membership determines whose OKRs you see in team views and who appears in owner dropdowns.

Activity

Activity shows edits, updates, and check-ins for this team only. Use it when you need team-scoped history instead of the home Recent activity feed.

Settings

Settings (requires edit team permission) includes team name, parent team, and update cadence. Deleting a team is available here for authorised users.

Team-level cadence complements organisation defaults; see Check-in Cadence.

Hierarchy and alignment

Child teams can sit under a parent team. Parent relationships affect:

• Team tree display on the Teams page and in Explore
• Supports parent key result linking on the Create tab
• Bottom-up view on the alignment map

Tips

• Name teams like your org chart: Clear names make Explore and alignment easier to read
• Set cadence when creating: Changing rhythm later is possible in settings but early consistency builds update habits
• Use My teams for daily work: Contributors can ignore the full directory and live in My teams
• Open OKR Cycles from the sidebar: Leads get a calendar-style list without hunting through periods one by one