Managing User Roles |
Click here (https://support.seagullscientific.com/hc/en-us/articles/9522154309399-Creating-and-Managing-User-Roles-in-BarTender-Cloud)
As an administrator, you can create and configure a new user role in BarTender Cloud and edit or delete an existing role.
-
To open the Roles page, click
on the header bar, then click Administration in the BarTender Cloud menu, select Security, then Roles.
BarTender Cloud provides default user roles that have pre-assigned permissions. The following default roles are available:
-
Print Operator: Users who have this role can print and reprint documents, manage printers, and view their print history.
-
Content Manager: Users who have this role can print and reprint documents and upload, organize, and manage files and folders.
-
API User: Users who have this role can perform the same tasks as users who have Print Operator and Content Manager roles can (print and reprint documents, manage files and folders, manage printers, and view print history), and they can also use the BarTender Cloud REST API from within your custom application.
-
Auditor: Users who have this role can manage files and folders and view print history.
|
Access to the BarTender Cloud REST API is included with the Automation subscription plan. |
|
Administrators can limit access to printers, files, and folders by granting or denying permissions to specific users and groups for specific items, regardless of user role. For more information, refer to Granting Access Permissions for Printers and Granting Access Permissions for Files and Folders. |
The following permissions are available:
-
Manage Documents: Permissions to upload organize and manage files.A role that is given Manage Documents permissions is also granted mandatory Print Access permissions.
-
Print Access: Permission to print labels from the Print Console.
-
Manage Printers: Allows access to Printer Management.
-
View Print History: Allows access to view print jobs.
-
Create Workflows: Allows access to workflow creation.
-
API User: Permission to submit POST and PATCH requests from Action API scripts.
The API User permission was designed to be combined with another set of permissions — Manage Documents, Print Access, or both. A role with only API User permissions would not be able to use the API to print or interact with documents without the Print Access or Manage Documents permissions, respectively.
To delete an existing user role
Related topics