Access Rights Recommendations

Access Rights Recommendations

1. Information Storage

RunMyProcess stores all production and test information in completely independent environments, ensuring the necessary separation to protect data.

2. Profiles and Restrictions

Every user registered in DigitalSuite is assigned a profile that determines their basic permissions. The available profiles are:

  • Admin: Full access to all elements of the customer account.

  • User: Limited access to specific elements, such as configurations and assigned project resources.

Additionally, administrators can apply further restrictions to control specific activities, such as:

  • Accessing DigitalSuite Studio.

  • Viewing data or metadata belonging to other users.

These restrictions apply to both DigitalSuite interfaces and applications built within it, ensuring that sensitive data remains protected.

3. Roles and Access Rights

To manage access at the project level, DigitalSuite uses roles that define the rights needed to carry out specific tasks. Roles can be organized into hierarchies and assigned to projects and users as needed.

Main roles at the project level:

  • Designer: Allows modifying project resources and running processes in Test Execution Mode. This role is suitable for developers.

  • User: Allows running interfaces in Live Execution Mode and completing assigned tasks. This role is intended for end users of the application.

Note: The Everybody role should be used with caution, as it grants universal platform access to all users within a specific project.

4. Recommendations

To ensure proper use of access rights, the following practices are recommended:

  • ADMIN Profile: Limit assignment to users who genuinely require full platform access.

  • Developers:

    • Create users with the USER profile.

    • Assign the Designer role within the corresponding project.

  • End Users:

    • Create users with the USER profile.

    • Assign the User role within the project.

  • Avoid broad use of the Everybody role.

  • For dynamic roles, consider using a Scripted role type, configurable with formulas that generate specific user lists.

For detailed information on profile- and role-level permissions, refer to the following link: RunMyProcess Digital Suite Documentation


    • Related Articles

    • Migrating to OAuth for Office 365 Mail in RunMyProcess

      Microsoft is retiring Basic Authentication for Office 365. For details, see the official announcement: https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750 Overview To use ...
    • Updating Certificates for SSO with SAMLv2

      When using SSO with SAMLv2 as the authentication method, you may encounter temporary access issues after updating your certificate. To ensure a smooth transition, keep the following in mind: Key Points to Remember Certificate propagation time After ...
    • Ticket submission guidelines

      To ensure timely and efficient resolution of your issues, please follow these guidelines when submitting a new ticket: 1. Choose the Appropriate Template Select the ticket template that aligns best with the nature of your report. Using the correct ...