Permission Set

• Used to identify the permission set in the UI, logs, and reports.
• Should be descriptive of the role or group it represents (e.g., "Designers", "Operators", "QA Reviewers").
• This value must be unique among all permission sets in the repository.

• Specify one or more user or group names. Supports Active Directory groups and users.
• Use the editor to select from available directory entries.
• A user receives the rights in this set if they are a member of any listed group or user.
• Membership is cumulative across all permission sets.

A combination of the following flags:

The Page Access property controls access to major areas of the Grooper user interface, such as the Design, Batches, Tasks, Imports, Jobs, Stats, Search, and Chat pages.

• Select one or more pages to grant access using the flag values of the Pages enumeration.
• If a user is a member of multiple permission sets, their access is cumulative (union of all sets).
• Restricting page access is a key part of implementing role-based security and limiting users to only the features they need.
• For example, grant 'Design' access to solution designers, 'Batches' and 'Tasks' to operators, and 'Stats' to managers.
• Use the 'Full' flag to grant access to all pages.

• Use this property to grant or restrict access to specific Node types, such as Project, Folder, or custom nodes.
• Each entry defines allowed commands and actions for the corresponding node type.
• Edited using a specialized editor for quick review and modification.

• Controls access to actions on attachments, such as files or documents linked to nodes.
• Each entry defines allowed commands for a specific attachment type.
• Use this to restrict or allow operations like view, add, or delete attachments.

• Controls access to actions on content links, such as references or relationships between nodes.
• Each entry defines allowed commands for a specific link type.
• Use this to manage who can create, edit, or remove links between content items.