Users and roles

This page covers managing the people in your client account, the roles and permissions that govern what they can do, the IP allowlist, and impersonation.

Users

Your client account is a Clerk Organization, and its members are managed through the built-in Clerk member panel on the Users page. From there you can:

• See members — everyone in the client account, with their email and status (active or invited).
• Invite a member — send an invitation to an email address, with their organisation role (admin or member) selected.
• Change a member's role — move someone between the admin and member roles.
• Remove a member — revoke their access.
• Manage pending invitations — view, resend, or revoke invitations that haven't been accepted.

These are Clerk's organisation roles. The richer VoC access model below — standard and custom roles, and the per-permission grants — layers on top to decide what each member can actually do inside the app.

Roles

A role is a named bundle of permissions. Davies CXsmart ships with standard roles and lets you create your own.

Standard roles

Standard roles are built in and shown with the permissions they include:

Role	Scope of access
System Admin	Full access, across the platform.
Client Admin	Full access within the client account.
Manager	Day-to-day management: dashboards (view + build/edit), reports, responses (view/edit/export), verbatim, surveys (view/edit/distribute), alerts, leads, badges, the AI Executive view, and competitor benchmarking.
Analyst	Read-and-analyse: dashboards, reports, responses, verbatim, surveys, alerts, leads (view), the AI Executive view, and competitor benchmarking.
Agent	Minimal: dashboard and responses (view).

Custom roles

On Roles & permissions you can create roles specific to your client account:

1. Select Create role and give it a name.
2. Tick the permissions it should include, grouped by category (Insight, Responses, Verbatim, Surveys, Alerts, Leads, Admin, Engagement).
3. Save, then assign the role to members.

You can edit or delete custom roles at any time. Standard roles are fixed and cannot be edited.

Permissions reference

Permissions are resource.action keys. A member's effective access is the union of all the permissions across their roles.

Permission	Allows
dashboard.view, reports.view	View dashboards and reports.
dashboards.manage	Build and edit dashboards.
responses.view / edit / delete / export	Work with responses.
verbatim.view, verbatim.code	View and code verbatims.
surveys.view / edit / distribute	Build and distribute surveys.
alerts.view, alerts.manage	View and manage alerts.
leads.view, leads.manage	Work with leads.
executive.view	View the AI Executive summary.
benchmark.view	View competitor benchmarking.
feedback.manage	Triage in-app product feedback.
badges.manage	Manage badges and coaching.
agents.manage	Manage agents.
users.manage, roles.manage	Manage members and roles.
account.manage	Manage workspace settings, segments, and the audit log.
integrations.manage	Manage webhooks and integrations.
compliance.manage	Manage suppression and compliance.
gdpr.manage	Run GDPR erasure and retention.

Every protected action checks the relevant permission and is refused if you lack it.

IP allowlist

In Workspace settings you can restrict access to a list of allowed IP addresses or prefixes. Add the IPs or prefixes your team uses; an empty list means access is open to all. This guards both the console and API access.

Impersonation

System administrators can impersonate a member to troubleshoot an issue from that person's point of view, without needing their password. Impersonation is an administrative capability used for support and is subject to audit.

Next steps

• Agents — colleagues attributed to responses (distinct from workspace members).
• Features & audit — see who changed what.
• Account — a member's own profile settings.