Skip to main content

Customer User Roles

This article defines User Roles and lists the Permissions included in each.

The User Role defines the default access and capabilities a user has when they log into the Hatz platform via a subdomain (like MSP123.hatz.ai). It sets the core actions they can perform, and establishes a baseline of permissions.

User roles ensure users have the essential tools to do their jobs effectively.

Below is a table that displays the Permissions included by default for each User Profile: Client Admin, General User, Chat Only User, and Workshop User. Note that the checks indicate which roles have the Permission included.

Permission

Client Admin

General User

Chat Only User

Workshop User

View Apps

✔

✔

✔

Copy Apps

✔

✔

Delete Apps

✔

✔

Create Apps

✔

✔

Secure AI Chat

✔

✔

✔

✔

View App Builder Page

✔

✔

✔

Manage Email Templates

✔

Invite Users

✔

Disable LLMs for Tenant

✔

Use LLM Gateway

✔

✔

✔

✔

Manage tenant LLM Gateway

✔

Change Own User Settings

✔

✔

✔

✔

Manage Users in Tenant

✔

Manage Tenant Admin Settings

✔

Reset MFA

✔

Academy Access

✔

✔

✔

✔

Create Personal API Tokens

✔

✔

✔

✔

View Community Workshop Items

✔

✔

Publish Community Workshop Items

✔

✔

View AI Phone Agents

✔

✔

Create Groups

✔

Manage Groups

✔

Share with Groups

✔

Community access depends on whether your workspace has Community enabled. To publish an item, you also need permission to manage its sharing settings. Your MSP partner can hide Phone Agents for your workspace.

Client Admins can also manage workspace API tokens, shared credentials, agent variables, integrations, compliance, usage limits, branding, and MFA. They can manage memory, personalization, subagent, and artifact settings, view audit logs and usage, and access Academy team reports.

Academy Access is what puts the Learn tab in a user's navigation and lets them browse the course catalog, enrol, take lessons, and earn certificates. Every default role now includes it, and a custom role starts with it ticked, so users see Learn as soon as Hatz Learn is enabled for your workspace. To keep Learn away from a particular group, create or edit a custom role and untick Academy Access — default roles cannot be edited. Viewing training reports for other people is a separate permission, View Academy Team Progress.

Check access from the user’s account

Choose the role the person needs for their work. This example shows the Client Admin role in the provisioning form, then opens Email Templates from that administrator’s account to check access in the intended tenant.

Did this answer your question?