You need to configure user groups in Dynatrace Managed to allow access to your monitoring environment or your Dynatrace Server.
A default administrator account is created during Dynatrace Managed installation. This account exists regardless of the authentication type you select (internal or LDAP). The default administrator account has cluster permissions.
You can manage users and groups through Cluster Management Console.
In Cluster Management Console, select User authentication > User accounts.
Select Add new user.
This option is available only if you're using an internal database, not LDAP.
In Cluster Management Console, select User authentication > User accounts.
Select the user.
Select Add in the Add group assignments section.
A group cannot be assigned if no permissions are specified for the group.
You can assign a predefined set of permissions to a group. Once a group is defined, you can add users to the group. Users can belong to more than one group and inherit the permissions of the groups that they belong to. You can modify or create groups to suit your needs.
Users assigned to groups with this permission are automatically given administrator access rights for all environments. They have access to Cluster Management Console and can manage your monitoring environments and Dynatrace Server. Users assigned to groups with this permission can also:
To access environment permissions
Dynatrace provides the following environment-level permissions. Select all that apply:
View environment: Allows read-only access to the environment. You cannot change settings or install OneAgent with this permission alone.
View environment permission is required for any of the other environment permissions, so View environment is automatically selected for the environment when you select any other environment permission.
Change monitoring settings: Allows changing of all environment settings. To install OneAgent, you must provide the Download & install OneAgent permission.
Download & install OneAgent: Allows download of OneAgent and installation on hosts. To change/edit settings, you must provide the Change monitoring settings permission.
*****
). Also allows manually triggering memory dumps.Manage security problems: Allows viewing and management of vulnerabilities reported by Dynatrace Application Security.
View security problems: Allows viewing (but not management) of vulnerabilities reported by Dynatrace Application Security.
For details on Application Security permissions, see Fine-tune permissions.
To access management zone permissions
Dynatrace provides the following permissions at the management zone level. (Download & install OneAgent and Configure request capture data are grayed out as they do not apply to management zones.) Select all that apply:
View environment: Allows read-only access to the entities within the management zone. To change/edit settings, you must provide the Change monitoring settings permission.
View environment permission is required for any of the other management zone permissions, so View environment is automatically selected for the management zone when you select any other management zone permission.
*****
)—see also Environment permissions above.Replay session data with masking: Allows replay of recorded user sessions with playback masking rules applied at the time of replay. Note that any data masked during recording is never captured and, therefore, always masked during replay.
Replay session data without masking: Allows replay of recorded user sessions without playback masking rules applied. Note that any data masked during recording is always masked during replay.
For Session Replay permissions to work within a management zone, the user also needs to have access to the requisite applications.
For details on management zones, see Management zones.
Manage security problems: Allows viewing and management of vulnerabilities reported by Dynatrace Application Security.
View security problems: Allows viewing (but not management) of vulnerabilities reported by Dynatrace Application Security.
For details on Application Security permissions, see Fine-tune permissions.
When you provide any permission other than View environment at the environment level, View environment is automatically enabled as well for the environment. Likewise, when you provide any permission other than View environment at the management-zone level, View environment is automatically enabled for the management zone.
Management zones are designed to provide targeted and limited access to certain entities within an environment. If you wish to provide a permission to users accessing a management zone, we recommend that you use the management-zone-level permissions. Any permission you provide at the environment level supersedes and adds to those at the management-zone level. In other words, management-zone permissions cannot be used to limit permissions already provided at the environment level.
Take the example of a management zone containing three hosts out of five total hosts in an environment. If you grant the View logs permission to the management zone, viewers can see the Logs tab with information for the three hosts in the management zone. However, if you remove the same permission at the management-zone level and provide it at the environment level, users will be able to:
User permissions can be also managed with IAM policies, which allow more fine-grained access control. With policies, you can craft your own access permissions and assign them to user groups on either the cluster or environment level just like with the permission mechanism.
To learn more, see Working with policies.