Skip to main content

User Roles & Permissions

DZDESK uses Role-Based Access Control (RBAC) to manage what users can see and do within the platform.

Overview

Each user is assigned exactly one role that determines their permissions. Roles are hierarchical, with higher roles having all permissions of lower roles plus additional capabilities.

User Roles

Admin

The highest privilege level with full system access.

Capabilities:

  • All Agent capabilities, plus:
  • Manage users and groups
  • Configure SLA policies
  • Set working hours and holidays
  • Access system settings
  • View all audit logs
  • Manage tenant configuration
  • Configure integrations

Typical Users:

  • IT Managers
  • System Administrators
  • DZDESK Administrators

Agent

Standard support staff role for daily operations.

Capabilities:

  • All Viewer capabilities, plus:
  • Create new requests
  • Edit requests
  • Assign requests to self or others
  • Change request status
  • Add comments and attachments
  • View group queues
  • Claim unassigned requests

Typical Users:

  • Help Desk Technicians
  • Support Engineers
  • IT Support Staff

Viewer

Read-only access for monitoring and oversight.

Capabilities:

  • View requests (scope may be limited)
  • View dashboards
  • Access reports (if permitted)
  • Search requests
  • Cannot create or modify data

Typical Users:

  • Department Managers
  • Executives needing visibility
  • Auditors
  • Trainees

Permission Matrix

PermissionAdminAgentViewer
View assigned requests
View all requests✓*
Create requests
Edit requests
Delete requests
Assign requests
Change priority
View all users
Manage users
Manage groups
Configure SLA
System settings
View audit logsLimited

*Agents see requests based on group membership.

Role Assignment

During Provisioning

When users first log in:

  1. Account is created from identity provider
  2. Default role is assigned (configurable)
  3. Administrator can change role as needed

Changing Roles

Administrators change roles via:

  1. Navigate to Settings > Users
  2. Find the user
  3. Click Edit
  4. Select new role from dropdown
  5. Save changes

Role changes take effect immediately.

Group-Based Access

Beyond roles, access is refined by group membership:

Group Visibility

  • Agents see requests in their groups
  • Requests can be assigned to group queues
  • Cross-group visibility requires Admin role

Multiple Groups

Users can belong to multiple groups:

  • See combined queue from all groups
  • Can be assigned requests from any group
  • Useful for specialists covering multiple areas

Special User Types

VIP Users

VIP designation adds:

  • Priority boost on their requests
  • Faster SLA targets
  • Special visibility to agents
  • Enhanced notifications

See VIP Users for details.

Service Accounts

For API integrations:

  • Limited to API access
  • No interactive login
  • Scoped permissions
  • Audit logged separately

Best Practices

Role Assignment

  1. Principle of Least Privilege: Assign minimum necessary role
  2. Regular Review: Audit role assignments periodically
  3. Documentation: Document why users have specific roles
  4. Separation of Duties: Don't give everyone Admin access

Group Organization

  1. Create groups based on expertise areas
  2. Keep groups focused and manageable
  3. Avoid excessive group overlap
  4. Review group membership regularly

Security Considerations

  1. Limit Admin accounts
  2. Use named accounts (not shared)
  3. Review access when roles change
  4. Remove access promptly for departures

Troubleshooting

User Can't See Requests

  • Check user's role
  • Verify group membership
  • Confirm request is in user's group

User Can't Perform Action

  • Review role permissions
  • Check if feature is admin-only
  • Verify user is active

Role Change Not Working

  • Ensure you have Admin role
  • User may need to log out/in
  • Check for sync issues with identity provider