- DigiCert product docs
- DigiCert DNS
- Manage account access
- DNS roles and permissions
DNS roles and permissions
Roles define what users and service users can access and do in DigiCert® DNS. Each role provides permissions for specific areas of the account, such as DNS zones, records, or identity and access management.
Explore the Roles page
To view roles in your account, go to Configuration > Access management and select the Roles tab.
The page displays the following information:
Column | Description |
|---|---|
Role | The role name. Select it to view its permission matrix |
Description | A summary of the access the role provides |
Type | The role’s classification. Built-in roles are identified as System |
Select a role name to view the actions it allows across each area of DigiCert® DNS. The permission matrix shows whether the role includes Create, Read, Update, and Delete permissions.
To review or change a user’s or service user’s assigned roles, open their profile and use the Roles and permissions section.
System roles
DigiCert® DNS provides the following system roles. Choose roles based on the access a user or service user needs.
Role | Access |
|---|---|
Account owner | Primary owner of the account with full administrative control |
Account admin | Full administrative control across the account and associated resources |
Account operator | Full control of DNS resources without access to identity and access management |
Account viewer | Read-only access across the account |
Account auditor | Read-only access to identity, access, and configuration settings |
Access manager | Full control of identity and access settings without access to DNS resources |
Zone admin | Full administrative control across DNS zones |
Zone editor | Permission to modify DNS records and related zone configuration |
Zone viewer | Read-only access across DNS zones |
How multiple roles affect access
When a user or service user has multiple roles, their permissions are combined. An action is allowed if any assigned role grants permission to perform it. A role with fewer permissions does not restrict access granted by another role. For example:
Assigned roles | Resulting access |
|---|---|
Zone viewer and Zone editor | Includes permission to modify DNS records and related zone configuration through Zone editor |
Account viewer and Account admin | Includes full administrative control through Account admin |
Account operator and Access manager | Combines control of DNS resources with control of identity and access settings |
Review all assigned roles when evaluating access. Adding a read-only role does not make an administrator’s access read-only. Similarly, removing one role only removes permissions that no other assigned role provides.
To reduce access, remove or replace every assigned role that grants the permissions the user or service user should no longer have. See DNS users and DNS service users for role assignment instructions.
Role permission matrices
A role’s permission matrix shows which actions it allows in each area of DigiCert® DNS. The matrix uses four permission types:
Permission | Action |
|---|---|
Create | Add resources |
Read | View resources and information |
Update | Modify existing resources or settings |
Delete | Remove resources |
A checkmark indicates that the role includes the permission for that area; for example, the Account admin role includes all four permissions across the following areas:
Area | Create | Read | Update | Delete |
|---|---|---|---|---|
Account management | ✓ | ✓ | ✓ | ✓ |
Identity and access management | ✓ | ✓ | ✓ | ✓ |
Users | ✓ | ✓ | ✓ | ✓ |
Roles | ✓ | ✓ | ✓ | ✓ |
Service users | ✓ | ✓ | ✓ | ✓ |
Tokens | ✓ | ✓ | ✓ | ✓ |
Zone management | ✓ | ✓ | ✓ | ✓ |
Record management | ✓ | ✓ | ✓ | ✓ |
Zone properties | ✓ | ✓ | ✓ | ✓ |
Traffic management | ✓ | ✓ | ✓ | ✓ |
Health checks | ✓ | ✓ | ✓ | ✓ |
Reporting and analytics | ✓ | ✓ | ✓ | ✓ |
Billing | ✓ | ✓ | ✓ | ✓ |
DNS users, roles, DNS service users, and DNS API tokens are part of identity and access management.
Review a role’s permission matrix before assigning it to ensure that its permissions match the intended level of access.