Planning your groups

Managing identities and devices at scale can be a complex task, especially when we consider that most of the time we see attribution policies in organization targeting the people and not the role.

Hopefully, Bravas is here to prevent that kind of mistake that could cost you a lot down the road. With Bravas, you are required to use groups to assign resources such as native apps or web services.

And we strongly encourage you to design your group list according to your set of roles and department in your organization.

Consider this simple example: if you are running a woodworking organization, you will not give a hammer to Alice and Bob because they are Alice and Bob, or you will not give them a hammer because they are part of the "hammer" group in your organization. You will give them a hammer because they are carpenters. That is their role in your organization that will define their right of use.

And the same goes for C-level people. Some privileges are not linked to the people but their position in the company. Being part of the EXEC, or being the active CTO.

Planning for groups even at that level will ease your future work when your CTO leaves, for example. You will perhaps have your two CTOs at the same time in the CTO group, allowing an easy transition between people in charge during a certain time.

To ease your start with Bravas, take a few minutes to create your initial groups representing your organization by going to the Configure tab, then in the Organization groups section on the left-hand menu.