Today, there are a limited number of roles someone can be given: Admin, Editor, etc.

While those are helpful, they don't allow organizations to custom build workflows or specific roles of people within Avo. By allowing a custom role option, you can set better and more accurate responsibilities for team members within Avo.

For example, we have two distinct groups of tracking plan approvers, and one person from each group must approve the tracking plan before it merges into main. With the current setup, we can identify that two people must approve before the merge, but we can't say "one of these three people in group 1 AND one of these four people in group 2" must approve before merge. In today's setup, we'd simply have to assign all seven people as Admins and set two approvers needed before a merge is allowed. But, that's not ideal, and requires a lot of work outside Avo to manage. Plus, that begins to make way too many folks admins within the system.

With the ability to create custom roles and set what those roles can/cannot do, we can build out our custom requirements for implementation. And, others can build out their sets of requirements too!