Use groups to manage permissions
Assigning roles and licenses to groups instead of individual users turns access management into membership management: when someone joins or leaves a team, you update one group membership instead of revising each of their assignments.
Overview
Almost everything assignable accepts a group: server and repository roles, item roles on a Permissions tab, licenses, and cycle groups. A user's effective rights combine everything their groups carry — additively, with vetoes winning — and the platform always shows the source: "inherited from group …" on the Edit User page, the profile, and the effective permissions view.
Two patterns cover most organizations:
- Mirror your org: one group per department or team. Assign each group the roles and licenses its members need. A group you create in iGrafx can contain other groups — including groups synchronized through SCIM — so you can nest teams under a department where that helps.
- Model access levels: groups like "Modelers" or "Risk managers" that carry a bundle of role assignments across repositories; put people in whichever level fits.
The built-in Everybody group contains every user automatically, so whatever you assign to it reaches all of them, including anyone added later. Use it for what everyone needs — it carries the User server role by default — and assign restricted roles, and any license you don't want every user to consume, to narrower groups.
When users are synchronized from your identity system, groups can come along with them — membership is then maintained in your directory, and iGrafx assignments follow it automatically.