Module 1 of 6 · 10 min

# Teams and User Management

Mirroring your organization structure with hierarchical teams, and managing the users inside them.

## Why this matters

A user was added to the wrong team eighteen months ago and has accumulated access nobody has reviewed since. This module covers teams, users and roles, and how to keep that from happening.

## Before you start

### Assign access to teams

Granting access to individuals produces a permission set nobody can reason about within a year. Granting it to teams means access follows organizational structure, and a joiner or leaver is a single change in one place.

### Team, role and user are three separate ideas

A team expresses who someone works with, a role expresses what they are allowed to do, and a user is the identity holding both. Keeping them distinct is what lets you move a person between teams without rebuilding their permissions.

### Provisioning is only half the lifecycle

Deprovisioning and periodic review are where most of the risk sits, and they are the parts usually left undesigned. Decide how access gets removed at the same time you decide how it gets granted.

## The interactive demo

Work through the demo below. It runs in your browser with nothing to install. Watch for:

*   •Where Team and User Management lives in workspace settings
*   •How hierarchical teams mirror your organization structure
*   •Creating a team and placing users in it

## After this module you should be able to

*   ✓Provision a user with the right team and role
*   ✓Explain why team based assignment scales and per user assignment does not
*   ✓Describe the deprovisioning half of the access lifecycle