Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | 20.11 This feature was updated in 20.11.
Maestro uses the following permissions to control user access to restricted content. The permissions are mapped to the standard roles, so you know what roles to assign to users to allow them to use certain product functionality. This is listed in the table below:
| Permission for Product Functionality | Description | Role |
|---|---|---|
|
Form Edit |
Allows users to edit a form. |
|
|
Form Publish |
Allows users to build a form. |
Maestro Administrator Maestro Developer |
|
Form Remove |
Allows users to delete a form. |
Maestro Administrator Maestro Developer |
|
Form View |
Allows users to view a form. |
Maestro Administrator Maestro Developer |
|
Library Edit |
Allows users to edit a library. |
Maestro Administrator Maestro Developer |
|
Library Remove |
Allows users to delete a library. |
Maestro Administrator Maestro Developer |
|
Library Share |
Allows users to share libraries. | 20.11 This feature was introduced in 20.11. |
Maestro Administrator Maestro Developer |
|
Library Share Global |
Allows users to share libraries globally. | 20.11 This feature was introduced in 20.11. |
Maestro Administrator Maestro Developer |
|
Library View |
Allows users to view a library. |
Maestro Administrator Maestro Developer |
|
Organization Edit |
Allows users to edit an organization. |
Maestro Administrator Maestro Developer |
|
Project Edit |
Allows users to edit a project. |
Maestro Administrator Maestro Developer |
|
Project Export |
Allows users to export a project. |
Maestro Administrator Maestro Developer |
|
Project Import |
Allows users to import a project. |
Maestro Administrator Maestro Developer |
|
Project Remove |
Allows users to delete a project. |
Maestro Administrator Maestro Developer |
|
Project View |
Allows users to view a project. |
Maestro Administrator Maestro Developer |
|
Release Edit |
Allows a Maestro Administrator to edit releases. |
Maestro Administrator |
|
Release Remove |
Allows a Maestro Administrator to delete releases. |
Maestro Administrator |
|
Release Version View |
Allows a Maestro administrator to view release versions. |
Maestro Administrator |
|
SCM Design Delete |
Allows staff who can use Maestro SCM to delete designs. |
Maestro SCM Design |
|
SCM Design Edit |
Allows staff who can use Maestro SCM to edit designs. |
Maestro SCM Design |
|
SCM Design View |
Allows staff who can use Maestro SCM to view designs. |
Maestro SCM Design |
|
SCM Org Library Add |
Allows staff who can use Maestro SCM to add organization libraries. |
Maestro SCM Org Library |
|
SCM Org Library Edit |
Allows staff who can use Maestro SCM to update organization libraries. |
Maestro SCM Org Library |
|
SCM Org Library View |
Allows staff who can use Maestro SCM to view organization libraries. |
Maestro SCM Org Library |
|
SCM Project Delete |
Allows staff who can use Maestro SCM to delete projects. |
Maestro SCM Project |
|
SCM Project Edit |
Allows staff who can use Maestro SCM to update projects. |
Maestro SCM Project |
|
SCM Project View |
Allows staff who can use Maestro SCM to view projects. |
Maestro SCM Project |
|
SCM Project Library Add |
Allows staff who can use Maestro SCM to delete project libraries. |
Maestro SCM Project |
|
SCM Project Library Edit |
Allows staff who can use Maestro SCM to update project libraries. |
Maestro SCM Project |
|
SCM Project Library View |
Allows staff who can use Maestro SCM to view project libraries. |
Maestro SCM Project |
|
Shared Domain Model Edit |
Allows staff to edit shared domain model. |
Maestro Administrator |
|
Versions Admin |
Allows staff to manage versions. |
Maestro Administrator |
Maestro doesn't have granular user access control to templates vs forms in the same project, so you can't allow users to modify form text in a form but refuse them to edit the form's styling.
As you have access to an organization, which is separate to your assigned permissions, you can't have read access to one organization or project and full write access to another organization or project.
However, you can have a separate organization for template developers and have the form in another organization and then utilize shared libraries that allows sharing of tagged libraries between organizations.
Next, learn how to view roles.