# RBAC Operational Workflow

### **Important notes before starting**&#x20;

1. Security Groups are created by IT administrator&#x20;
2. One user can be in only one security group at a time&#x20;
3. One security group can be mapped to only one vertical.&#x20;
4. One security group can be used for multiple roles in single vertical&#x20;
5. Users cannot log in if they are not assigned to any vertical and mapped with any project&#x20;

### This document Includes:

[Account Admin Mapping](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/account-admin-mapping)

[Login to Avo Assure with SSO](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/login-to-avo-assure-with-sso)

[Vertical Management](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/vertical-management)

[Project Management in Vertical](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/project-management-in-vertical)

[Agent Management in Vertical](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/agent-management-in-vertical)

[Vertical Admin](https://docs.avoautomation.com/administration/vertical-management/rbac-operational-workflow/vertical-admin)
