🔍Note: This page covers User settings of “MS Teams-based” services. Users in a “Skill-based” service are configured via "Agents" tab instead.Â
PRECONDITIONS
All Nimbus services allow User Management, however Advanced Routing or Enterprise Routing primarily operate in sync with MS-Teams. In a Contact Center service, users can be managed manually. More info on this can be found under User Assignment Types.
For Tenant Admins:Â
- Nimbus Service Provisioning needs to be concluded for at least one MS Teams Team,
⮑ Within the Service Administration  the service will shows as “MS Teams-based” User Assignment Type. This will signal that the Nimbus users are in sync with the corresponding MS-Teams Team. -  A “Users” tab within the Service Administration allows to configure further roles. Refer to Service Permissions for more details.
For Team Owners:
- Within your MS Team Team you need to invite additional members and owners to participate in the Nimbus service.
- In the “Users” Tab described on this page you can manage the "Active" state of your users.
General Settings
| Setting | Description |
|---|---|
| Default Team Owner Role |
Determines which User Roles a user is granted once he joins the team. 💡 This field is read-only. To change this you need to access the service settings via Service Administration. |
| Team member can change the active state | Allows or disallows team members to change their active state.Â
đź’ˇ Team owners and users with the "Workflow Admin Limited" role assigned to them can still change the active state of all team members via the service settings page. |
Users
| Setting | Description |
|---|---|
| Name | |
| UPN |
💡 Fields are read-only. Users are auto-synced via MS-Teams.
|
| Role |
Roles are in sync with MS-Teams channel “Owner” and “Member” roles. 🔎 Via Service Administration  > Users tab any administrator can further adjustments. Read Service Permissions and Portal Roles for more details. |
| Active | Steers the user's availability to take tasks within Nimbus.
|