Team & Access

Invite users, give them a role, group them into teams, and organize your workspace with custom categories.

#Inviting users

The Users page is your team roster. Filter by role (All / Admin / Manager / Employee / Viewer) or status (All / Active / Inactive). Search filters by name or email.

Click Invite User to add a new team member. A magic-link email is sent to the address you provide — once they complete the flow, they appear as Active.

FieldTypeDescription
email*emailInvitation target.
firstName*textGiven name.
lastName*textFamily name.
role*dropdownAdmin, Manager, Employee, or Viewer (see roles below).
phonetelOptional phone number.

#Roles

S
Search...
DB
Roles & Permissions
26 team members · 4 roles
RoleMembersPermissionsAccess
Owner
1All permissionsConfigured
Admin
3Manage team & billingConfigured
Member
8Projects, clients, contractsConfigured
Client
14Portal access onlyConfigured
Granular Permissions
View clients
Edit invoices
Delete contracts
Audit Log
14:02 · Admin role updated
09:18 · New member invited
Yesterday · Owner role unchanged
The four built-in roles and where they apply
  • Admin — full access to the workspace, including billing and user management.
  • Manager — everything except billing and destructive org-level actions.
  • Employee — day-to-day work: clients, projects, invoices, cases, documents. No user admin.
  • Viewer — read-only access to most screens. Can’t create or edit.

Role changes apply immediately. Toggle a user between Active and Inactive from the row menu — inactive users can’t log in but keep their historical records (assigned items, activity trails).

Not yet available
Roles are fixed at four today. Custom roles, fine-grained per-feature permissions, and SSO/SAML are not yet supported.

#Teams

Teams groups users together for lighter-weight structure than roles — for example, to tag who’s on the Sales team or the Delivery team. If no teams exist yet, use Initialize Teams to create the defaults, then add members.

Per member you set:

FieldTypeDescription
userId*comboboxA workspace user.
roledropdownMember or Lead inside the team.
isLeadcheckboxConvenience flag — same as setting role to Lead.
Not yet available
Teams are currently a tagging layer. Team-scoped permissions, team-level channels, and team settings pages are not yet available.

#Categories

S
Search...
DB
Categories
Custom taxonomy across clients, projects, cases
NameParentApplies ToDescription
EnterpriseClientLarge accounts over $100k ACV
SMBClientSmall to mid-market
ReferralLeadClientInbound referral source
Website RedesignTemplateProjectReusable project type
Billing IssueSupport CasePayment & billing problems
Feature RequestSupport CaseCustomer feature asks
Custom categories applied to clients, projects, and support cases

Categories is your taxonomy layer — hierarchical tags you apply to clients, projects, and support cases for grouping and reporting. Each category has:

FieldTypeDescription
name*textDisplay name.
descriptiontextShort explanation of what belongs here.
parentIdcomboboxOptional parent category — lets you build hierarchies like Industry → Finance → Banking.
targetEntity*dropdownWhere this category applies: Client, Project, or Support Case.

Categories appear in the relevant combobox when you create or edit that entity type. Deleting a category removes the tag from records but doesn’t delete the records themselves.