Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Specifying the production level

Updated on August 25, 2021

In on-premises systems, administrators can specify its production level, thereby defining operator access and permission to make changes to the system. Production levels control the types of permitted changes and specify the purpose of the environment, for example, development or production.

Pega supports the use of a production level to establish a security scheme that defines the permissions for users of that Pega instance: the more restrictive the security scheme, the fewer users who can edit application rules. In development environments, in which developers need to create and update rules with minimal restrictions, development teams often prefer a lower production level, typically level 2, which has fewer restrictions than higher levels. When you log in to Dev studio, you can find the current production level displayed in the upper-right corner of your screen.

In Pega Cloud Services environments, beginning in Pega Platform 8.4.1, clients cannot change the default production levels that Pega sets for all environments within each Pega Cloud subscription, depending on the client use of the environment:

  • 2 – Development/Test environments
  • 4 – Staging environments
  • 5 – Production environments

    Pega Cloud does not support requests to modify these levels.

For on-premises systems, clients can modify the production level for their system.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the SysAdmin category, and then click System.
  3. Click the name of the system for which you want to specify the production level.
  4. In the Production level list, click one of the following options:
    • 1 - Sandbox
    • 2 - Development
    • 3 - Quality assurance
    • 4 - Staging
    • 5 - Production
  5. Click Save.
What to do next: Restart your system for the production level changes to take effect.
  • Previous topic Specifying system-wide security parameters by using system data instances
  • Next topic Specifying the environment name

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us