Central config setting to prevent users from creating or editing environments

Version/Environment (if relevant):

All versions

Issue:

In some organizations, Domino Admins may need to restrict users so that they cannot create new environments or edit existing environments.

Resolution:

Domino Admins can add this Central Config setting related to Environments and set it to false:

com.cerebro.domino.environments.canNonSysAdminsCreateEnvironments

• If set to true (default), non-admins can create and edit environments.
• If set to false only system administrators can create and edit environments.

Reminder that you must restart the Domino services for changes to take effect. 

When set to true, users can create new environments. Users can also edit their existing environments. 

Environment Visibility

When a user creates a new environment, the visibility is Private by default. Users do not have permissions to edit visibility. Only Admins can make the environment Globally Accessible, which makes it available to all projects. Users would need to ask the Admins to switch their environment's visibility to Globally Accessible or Available to an Organization.

When set to false, users cannot create new environments. There is no Create Environment button available to users.

Users cannot edit environments that they had previously created. They'll see a message: You are not authorized to create compute environments. Please contact your Domino Admin if you have any questions.

Notes/Information:

Related: Which Central Config key dictates who can edit Compute Environments?

For more about making a specific environment available to a specific group of users, please see Typical uses for organizations > Share compute environments.