Groups vs. Roles

fungu5

Hello, I am having some difficulty understanding the different use cases for groups vs. roles within a project. It seems they have very similar functionality. What are the capabilities of each, and when is it recommended to use one over the other? Thanks!

Andrew_Decisions

Hello! Thank you for using Decisions support!

The purpose of Groups is to create collections of user accounts that share similar responsibilities or system access permissions.

The use case for groups is to apply permissions and create group-specific pages and dashboards. For example, you might have groups for Testers, Developers, Marketing, and Admins.

Here is link to our documentation about creating groups that may assist you.

v9 Creating Groups

https://documentation.decisions.com/docs/creating-groups

The purpose of roles are task identifiers that allow administrators to add accounts and groups as a specific role.

The use case for roles is for specific assignments, like assigning a task to a 'Development Team Lead' role, which might include the 'Developers' group and specific team leaders.

Roles can be used to define recipients for assigned Decisions objects such as tasks, forms, reports, pages, or service catalog items.

Here is a link to our documentation about assignment roles that you may find useful.

v9 Assignment Roles

https://documentation.decisions.com/docs/assignment-roles

v9 Creating and Using Assignment Roles

https://documentation.decisions.com/docs/creating-and-using-assignment-roles

As a recommendation, use Groups when you need to manage permissions and access for a collection of users with similar responsibilities.

Then, use Roles when you need to assign specific tasks or responsibilities to users or groups, often involving more dynamic or hierarchical assignments.

Thank you again for reaching out to us!

Best regards,

Andrew || Decisions Support