Permission Descriptions for Users and Groups
Understand how each permission affects access for users and groups.
- Edit Processes
While permissions apply to users, those permissions can be assigned from a user account or a group:
- User-level permissions: Permissions can be assigned to a user account. These permission assignments only apply to that user account. From user-level permissions, you can assign Administrator-level permissions or all permissions to a user account. Instead of assigning individual permissions to a user account, the following options are also available:
- Super Admin: Assign the Make this user a Super Admin option to grant unrestricted access to the entire ProcessMaker Platform instance. In doing so, ProcessMaker Platform does not check permissions for user accounts with this setting selected, allowing such users to administer and install packages which might otherwise require permissions be granted to a user account to perform. Users whose account have this setting may do the following:
- View the Tasks as displayed in the Task column of Request summaries by clicking a link to that Task. Users that do not have the Make this user a Super Admin option do not have a hyperlink to Tasks from Request summaries.
- See all comments in a Request and a Task summary.
- Upload file in API - Settings.
- Filter by any user in API - GroupMember.
- Run Script Executor in APIs.
- Link to edit any task in Request Detail.
- Reassign any open or overdue Task.
- All permissions: Assign the Assign all permissions to this user option to assign all permissions to that user account.
- Group-level permissions: Permissions can be assigned to a group. A group assigns the same permissions to all user account members. Using groups makes it easy to manage permissions for multiple user accounts with identical permission assignments. From group-level permissions, you can assign all permissions to a group. See Edit a Group.
User-level and group-level permission assignments are cumulative. This means that a user account has all the group-level permission assignments from all its group memberships, but also has the flexibility of permission assignments that apply only to that user account. For example, a user account might be a member of a group whereby its members can view the list of all Processes. However, an Administrator can assign the permission to edit Processes to only the one user account.
See the following best practices when organizing group members:
Create groups based on how you define user roles in your organization. Based on how you define user roles, assign permissions to groups so that all group members have the same permission set. Below is an example how you might create groups to assign permissions:
- User: Most users start or participate in Requests and perform Tasks. Their permission assignments may be limited to Requests. Note that if you want specific users and/or groups to start and/or cancel Requests, those must be set from the following functional areas and are outside the scope of the permission settings discussed in this topic:
- Process Designer: Process designers create Process models. Their permission assignments may be limited to Decision Tables, Environment Variables, Processes, Process Templates, Requests, Saved Search, Screens, Version History, and Vocabularies categories.
- Developer: Developers often create Scripts. Their permission assignments may be limited to Collections, Data Connectors, Files (API), Notifications (API), Requests, Scripts, Task Assignments (API), and Webhooks categories.
- Administrator: Administrators administer the ProcessMaker Platform environment and its users. Their permission assignments may be limited to Auth Clients, Collections, Comments, Groups, Requests, Translations, and Users categories. Assign specific Administrators in their user accounts the Make this user a Super Admin option.
Organize the role-based groups into larger groups so that permissions overlap amongst group members. Consider the following example.
Suppose that a group named "Process Modelers" with a set of permission categories to design Process models. This group has assigned to it the following permission categories:
A second group named "Process Architects" has a different set of permission categories from which to maintain Process Template consistency across their organization:
Senior managers within the organization that must have all these sets of permission categories. Instead of a third group that contains all five sets of permission categories, create a third group called "Senior Managers" that includes the "Process Modelers" and "Process Architect" groups. The "Senior Managers" group inherits the permission categories of the groups within it.
Permissions are organized into categories. Permissions are described below by category and how each permission affects ProcessMaker Platform functionality. These permissions function identically in user accounts and groups.
The Analytic Reporting package must be installed for the Analytics category of permissions to display.
The Analytics Reporting category contains the following permissions:
- Create Analytics: Create an Analytic Report from the Analytics page. Selecting this permission also selects the Edit Analytics permission. See Create an Analytic Report.
Select the View Analytics permission to use any of the other permissions in this category.
The Auth Clients category contains the following permissions:
- Create Auth Clients: Create a client authentication key on the Auth Clients page. Selecting this permission also selects the Edit Auth Clients permission. See Create a New Client Authentication Key.
- Delete Auth Clients: Delete a client authentication key from the Auth Clients page. See Delete a Client Authentication Key.
- Edit Auth Clients: Edit a client authentication key from the Auth Clients page. See Edit a Client Authentication Key.
- View Auth Clients: View all client authentication keys on the Auth Clients page. See View All Client Authentication Keys.
Select the View Auth Clients permission to use any of the other permissions in this category.
The Collections category contains the following permissions:
- Create Collections: Create a Collection from the Collections page. Selecting this permission also selects the Edit Collections permission. See Create a New Collection.
- Truncate Collections: Delete all records in a Collection using the
TruncateCollection
Data Connector Resource for that Collection. See Resources for Collections.
Select the View Collections permission to use any of the other permissions in this category.
- Create Comments: Post or reply to a Request or a Task comment. Selecting this permission also selects the Edit Comments permission. See the following sections:
- Delete Comments: Delete one of your Request or Task comments. You may only delete comments that you created. See the following sections:
- Edit Comments: Edit one your Request or Task comments. You may only edit comments that you created. See the following sections: