Skip to content
Platform

Teams

A Team is a named group of administrators. Instead of assigning roles to each administrator individually, you grant roles to a Team and manage who belongs to it; every member inherits the Team’s roles. A Team can hold different roles in different contexts, so one team can administer a Sign-In context while holding read-only access to an EntryPoint context.

At a glance

What it is
A named group of administrators that holds roles
Members
Administrators (not end users); they inherit the team's roles
Roles
Granted to the team; different roles per context are supported
Scope
Organization and MSP partner
Source
Created manually, or synchronized from an IdP group via SCIM

Creating a team and granting it roles are two separate steps, kept apart on purpose:

  • Create the team and manage its members on the Teams page. A new team starts with no authority.
  • Grant roles to the team under Administrators, on the Teams tab, at the organization level or inside any context. The same team can be given one set of roles in one context and a different set in another.

This separation means you can change who belongs to a team without touching what the team is allowed to do, and the reverse.

A person can be added to a team only if they are already an administrator (member) of that organization or MSP partner. If you add an email address that is not yet a member, Netgraph offers to invite them as a member first; they must accept the invitation before they can sign in.

A team is created at the organization or MSP level, but it can be granted roles in each service context independently. Across the contexts of an organization (for example Sign-In, EntryPoint, Meraki WPN, Cisco ISE) a single team can carry exactly the roles each context needs.

A group synchronized from your identity provider through SCIM appears as a Team whose membership follows the IdP group. SCIM keeps the membership in step but never assigns the team’s roles; an administrator maps the team to roles in Netgraph as above.

Next