Working with Teams

A team is where the day-to-day work of MonsterOps happens. Each team sits inside the Organization and is organized into a set of tabs for tracking priorities, metrics, action items, and meetings. This article gives you the map.

How a team is structured

When you select a team from the left-side navigation, you open it. Every team includes the following tabs:

• Team Dashboard — a roll-up view of the team's KPIs, To-dos, Rocks, and Issues at a glance
• News — team updates, announcements, and activity
• Rocks — the team's quarterly priorities, with milestones and progress tracking
• KPIs — the statistics the team uses to measure performance
• To-dos — short-term action items and follow-ups
• Issues — obstacles, risks, and unresolved questions
• Meetings — structured team sessions built on Agendas (Live Meetings, Past Meetings, and Agendas)

In addition, every team has its own three-dot menu in the left-side navigation, which opens two admin areas:

• Team Members — the people on this specific team, with the ability to invite new members and approve email domains
• Team Settings — team-level configuration like the team name, integrations, scorecard import, and the danger zone

Team-level vs. Organization-level features

Many concepts in MonsterOps exist at both the team and Organization levels, and it's worth understanding the difference:

• Team level: News, Rocks, KPIs, To-dos, Issues, Meetings, Team Dashboard, Team Members (per-team), Team Settings
• Organization level: Objectives, Org Chart, Core Values, Billing/Plan, Organization-wide Team Members, Settings

Some terms overlap — for example, "Team Members" exists at both levels. The team-level Team Members section only covers who's on a particular team; Organization-level Team Members covers everyone in the Organization and their permission levels.

Similarly, "Settings" exists at both levels but with different scope and different permission rules. Team Settings is open to any team member; Organization Settings is gated to Owners and Admins.

Permissions inside a team

Most everyday actions inside a team are open to all team members, regardless of their Organization-level permission level (Owner, Admin, or Member). This includes:

• Creating, editing, archiving, and deleting items (News, Rocks, KPIs, To-dos, Issues)
• Adding Notes to those items
• Linking items together (including linking Rocks to existing Objectives)
• Inviting new team members by email
• Changing Team Settings (name, integrations, scorecard import request)
• Creating a new team
• Creating meetings and acting as host
• Editing meeting notes from Past Meetings
• Rating attendees and managing the meeting (if you're the host of that meeting)

A few actions inside a team are restricted to Owners and Admins. Members can attempt them, but they'll see a red "Only organization owners or admins can perform this action" popup if they try:

• Approving email domains in Team Members
• Removing existing members from a team
• Directly creating, editing, archiving, or deleting Objectives (Members can still influence Objectives indirectly by linking their Rocks to them)
• Adding, editing, or deleting roles in the Org Chart

The most restricted action is in the Danger zone of Team Settings, where deleting a team is restricted to the Organization Owner and Super Admins (an internal access level above Owner / Admin / Member). Regular Admins cannot delete teams through the product.

See the individual articles below for more on how each team tab works.

Related articles

• Using the Team Dashboard
• Managing Team Members
• Team Settings
• Using the News tab
• Using the Rocks tab
• Using the KPIs tab
• Using the To-dos tab
• Using the Issues tab
• Using the Meetings tab
• Building and managing Agendas
• Working with your Organization