Splunk AppDynamics uses Role-Based Access Control (RBAC) to set user permissions and privileges for only those functions necessary in defined job responsibilities. Each user account can have varying levels of access based on their role(s). SeeManage Custom Roles for Splunk AppDynamics.

The Controller Tenant can authenticate users against local user accounts or external LDAP or SAML-based authentication providers. The user account for a Controller Tenant user authenticates through the Cisco Customer Identity (IdP) in the cloud rather than by an external authentication provider. See External Authentication for SaaS Deployments.

A group is a collection of users with a given set of permissions that apply to the users in the group. You can use groups to manage roles collectively

A role is a collection of permissions defining user actions; RBAC. When you assign a role to a user, they inherit the role permissions. A user's group membership and role remain constant for the duration of their login.

Permissions grant users the ability to perform an action on the platform. You can set permissions at a granular level to determine:

• The business applications the user can monitor.
• The parts of the UI that are visible.
• Types of configurations a user can make.