Skip to main content
Building a role for one job? Follow Build a Custom Role, a step-by-step walkthrough with screenshots.
Hiveku gives account admins granular control over what each user can access. Every member is assigned a role, and that role decides which departments they see and what they can do inside each one.
Access is the combination of two things: your plan (which features the account has) and your role (what you’re allowed to do with them). You see a feature only if your plan includes it and your role grants it.

How access works

Each department (Accounting, CRM, Marketing, Helpdesk, Communications, and so on) is broken into resources. For every resource, a role grants one or more capability levels: When a role doesn’t grant View on a department, that department is hidden from the sidebar entirely — it isn’t an upsell, the person simply doesn’t work in that area. (A feature your plan doesn’t include yet shows as a locked “Upgrade” item instead.) Inside a department you can see, a page can still need a permission your role doesn’t have, such as Calls in Communications. Opening it brings you back to the dashboard with a short note. It names the page (for example Communications > Calls), says whether your role or the account’s plan leaves it out, and says who can change it.

Default roles

Every account starts with nine built-in roles. You can assign them as-is or clone one as the starting point for a custom role. To see every box a default role holds, open Settings > Team Members > Manage Roles and click View next to the role. The table sums up each department in one word:
  • Full: every box in the department, including Manage where the department has one (Discussions has none, so Full there is View, Create, Edit and Delete).
  • Edit: View, Create, Edit and Delete, without Manage.
  • View: see only.
  • —: the department is hidden for that role.
A footnote marks a department where the rows differ.
  1. Websites, edit and publish: Projects and Database: Edit. Deployments: Manage, so they can put a site live. Hosting & Domains and Env & Secrets: View only.
  2. Finance, CRM: View on every CRM row, and every box on Invoicing & Estimates (send, void and record payments).
  3. Finance, Commerce: Products, Subscriptions and Reviews: Edit. Orders: View and Edit. Commerce Settings: View only.
  4. Own time only: Accounting is otherwise hidden, but they log their own hours and ask for their own time off (My own time and time off).
  5. Sales and Support, Communications: Calls, SMS and Extensions: Edit. Recordings: View and Delete. Comms AI Agent: Edit. Phone Numbers, IVR & Routing, E911, Supervisor Tools and Voice Settings: View only.
  6. View, no payroll: View on every Accounting row except Payroll, which is hidden, so they never see other people’s pay. They log their own hours and ask for their own time off. Members can also edit the Accounting AI Agent’s memory; its money actions still wait for an approval from someone with the matching right.
  7. Member, CRM: Edit on records (contacts, companies, deals, activities, sequences, invoicing, scheduling). Reports & Insights and CRM Settings: View only. They don’t see teammates’ calendars and can’t send email as a teammate.
  8. Member, Communications: their own calls (mark a voicemail heard, save a disposition or note) and texts (send an SMS or MMS), and Edit on the Comms AI Agent. Phone numbers, extensions, IVR, E911, supervisor tools and voice settings are View only.
Every role sees the account home and its own dashboards; see Dashboards and team activity. The Chief of staff rows (Agent Jobs, Account Soul) are Full for Owner, Admin and Manager and hidden for every other role.
Owner and Admin always have full access to everything the account’s plan includes — you can’t lock an owner out of their own account. For every role, the plan is the ceiling: a box never opens a feature the plan doesn’t include.

Member vs Admin

Admin has every box in every department the plan includes, and every setting: team members, roles, security, billing, connectors and notifications. The one thing an Admin can’t do is transfer ownership of the account. Member is a general editor. A Member can:
  • edit and publish websites;
  • work in CRM, Marketing, Helpdesk, PM Projects, Discussions and boards (create, edit and delete);
  • view Workflows, Commerce and Accounting, but not payroll beyond their own time;
  • handle their own calls and texts.
A Member can’t change account settings, billing, the team or roles, or phone settings (numbers, extensions, IVR, E911 and voice settings).

Project management access

PM Projects has its own rows in the role editor: Projects, Tasks and Milestones. The default roles hold these: What the two main rows control:
  • Adding a task needs Tasks: Create. It applies on the PM Projects page, in the website editor’s Tasks tab and in Workspaces. Starting a project is a separate permission (Projects: Create).
  • Workspaces follows the permission in each row’s own workspace. Workspaces shows projects from every workspace a person belongs to. Editing a project or a task, or adding a task, needs the permission in the workspace that owns it. Someone who can only view there sees plain values and no add field.
See Project Management for how each of these shows up on the page.

Custom roles

Admins can build roles with exactly the access a person needs — for example a “Bookkeeper” who manages Accounting and reads CRM but never sees Marketing.
1

Open Manage Roles

Go to Settings > Team Members and click Manage Roles.
2

Create or clone a role

Click New role, or Clone a default role to start from its access and adjust.
3

Set access in the matrix

For each department and resource, check the capabilities to grant (View / Create / Edit / Delete / Manage). Use the None / View / Full shortcuts to set a whole department at once.
4

Save and assign

Save the role, then assign it to people from Team Members.
You can’t grant a role more access than you have yourself, and you can’t delete a role while members are still assigned to it — reassign them first.

Dashboards and team activity

Dashboards have their own resources in the role matrix, under Dashboards and Team. A dashboard never shows anyone a number their role hides: each widget is checked against its own department, whoever built or shared the dashboard. Each person always sees their own team activity counts, with or without Team activity: View.

Owner and Admin

  • Owner — full control, including billing and transferring ownership. There must always be at least one owner.
  • Admin — full control except transferring ownership of the account.
Both bypass the role checks above, so they can always reach every part of the account their plan includes.

Websites: branches, versions and publishing

Branches, versions, reviews and the merge line follow the Websites › Deployments resource: Project history follows Websites › Projects: View lists restore points, and Create saves one and restores. Environment variables and environment groups follow Websites › Env & Secrets: View shows them (never a sensitive value), and Manage changes them and links groups to sites and unlinks them.
  • Only an owner or admin changes Branch settings, puts a review at the front of the merge line, dismisses someone else’s review, or deletes someone else’s comment.
  • Approving a review takes a person signed in to Hiveku. AI tools comment and ask for changes, but never approve.
  • By default, Owner, Admin, Manager, Marketing and Member can manage deployments, Viewer can view them, and Finance, Sales and Support do not see them.
  • An AI tool connected with a person’s key can do only what that person’s role allows. See Branches and AI tools.

AI connections

An AI connection (Claude, ChatGPT, the VS Code extension and the like) acts with the role of the person who created it. A key is never stronger than the person who made it: someone whose role cannot change anything can only create read-only keys. For the actions below, Hiveku also checks that person’s current permissions on each request, so changing their role changes what the connection may do.
  • Working on tasks through a connection needs its creator to have the right the app asks for: PM Projects > Tasks: Create to add a task, comment, file, time entry or recurring schedule, Tasks: Edit to change, complete, claim or reassign a task, and Tasks: Delete to delete one. Without it the connection is refused with a plain-words message saying who can grant the access. In a person’s chat, your department agents and your chief of staff follow the same rule for tasks (below).
  • Deleting a project-management project or a website needs the creator’s delete permission and a connection that belongs to a person. Hiveku’s own AI agents archive projects and cannot delete projects or sites, and a key with no recorded creator cannot delete either.
See LLM Connectors for the full list.

Your AI agents and tasks

In a person’s chat, your sales, support, marketing, Outbound, production and accounting agents, and the website builder’s AI, do only what that person’s role allows with tasks. Adding a task, commenting on one, or handing work to another department needs PM Projects > Tasks: Create, as adding a task does in the app; seeing the tasks handed to a department needs Tasks: View; changing or deleting a task needs Tasks: Edit or Tasks: Delete. Your chief of staff asks the same before it adds, changes, comments on or hands off a task. The website builder’s AI also asks PM Projects > Projects rights before it creates, changes or deletes a project. When the role is missing a permission, the agent tells you, and an account owner or admin can turn it on under Settings > Team Members > Manage Roles. Work an automation runs on its own, such as a workflow step or a scheduled job, is not limited by a role.

What’s Next?

Team Members

Invite people and assign their roles

Build a custom role

Step-by-step guide to the role matrix