Roles
Hiveku ships nine default roles, and admins can build custom roles with exactly the access a person needs. The most common defaults:
See the full capability matrix and how to build custom roles in the Permissions reference.
Inviting team members
1
Open Team Members
Go to Settings > Team Members and click Invite.
2
Enter email and role
Under Invite New Member, type the invitee’s email address and select a role from the dropdown (any default role except Owner, plus your custom roles).
3
Send invitation
Click Send Invite. The invitee receives an email with a link to join your workspace, and they’ll get the role you chose when they accept.
Seats
The top of the page shows how many of your plan’s seats are used, for example “4 of 5 seats used”. Pending invitations count toward seats. When every seat is in use, Invite is switched off: remove a member or cancel a pending invitation to free a seat, or upgrade your plan.Pending invitations
Invitations that haven’t been accepted yet appear under Pending Invitations. For each one you can:- Copy invite link — share the invitation link directly
- Resend invitation — send the invitation email again
- Cancel invitation — revoke it before it’s accepted
Access scope
What a member can see and do is controlled by their role. Roles gate access at the department level — Accounting, CRM, Marketing, Helpdesk, Communications, and so on — and by capability (view, create, edit, delete, manage) within each. A member only sees the departments their role grants, on top of what the account’s plan includes.For example, a Finance role sees Accounting and a read-only CRM, but never Marketing. Build roles that match how your team actually works in the Permissions reference.
Changing roles
From the three-dot menu next to a team member, choose Change Role and select a new role (default or custom) from the dropdown. The change takes effect within a few minutes. Owners can hand the account to someone else with Transfer Ownership in the same menu.Removing members
Open the three-dot menu next to a team member, click Remove Member and confirm. They lose access to the workspace and all its projects immediately, and the AI connections (API keys) they created in this workspace are switched off. Their commits and deployments remain in the history.Removing someone from a team is not the same as deleting the account they call home. If this workspace is their home account, removing them here does not change that, and deleting the workspace later would remove them from every account they belong to.
What happens to their project-management comments and hours
What Hiveku does with a person’s task comments and logged hours depends on whether this was the last workspace they belonged to.- They still belong to another workspace. Their comments and hours here stay as they were.
-
This was their last workspace. Hiveku deletes the person’s user completely, not only their place in this workspace. With it go:
- the comments they wrote on this workspace’s tasks, and
- the hours they logged on this workspace’s tasks, except hours that a finalized or paid payroll run counted. Those hours stay, so the payroll record keeps the hours it paid, but they are no longer linked to the person and show as Former member.
This is the same protection that stops a task or a project from being deleted while a finalized or paid payroll run counts its hours.