Skip to content

Team & Permissions

CryptaCount’s role-based access control provides granular permissions across three role tiers plus 42 workspace-level permissions, designed for the workflows of accounting practices and audit teams.

Navigate to Team in the sidebar (visible only to Owner and Manager roles). From here you can invite members, assign roles, and manage access.

Team management page with member list

Click Invite Member, enter the person’s email address, and assign their roles. They’ll receive an invitation email with a link to join.

CryptaCount uses a three-tier role system. Each tier controls a different dimension of access:

System-level access for platform operations. Most users don’t have a platform role — these are for CryptaCount staff only.

Permissions within a specific company:

RoleCan do
OWNEREverything — billing, deletion, all settings, ownership transfer
MANAGERManage workspaces, team members, settings. Cannot delete company or manage billing.
MEMBERWork with data — transactions, reports, assets. Cannot invite team or change settings.
VIEWERRead-only access to all company data

Permissions within a specific workspace:

RoleCan do
OWNEREverything — workspace deletion, ownership transfer
MANAGERManage wallets, team, integrations, settings
MEMBERWork with transactions, reports, assets, journal entries
VIEWERRead-only access to all workspace data

Beyond workspace roles, CryptaCount supports 42 granular permissions that provide fine-grained control over specific actions. Permissions cover these resource types:

ResourceAvailable Permissions
workspaceview, edit, delete
usersview, invite, edit, delete
walletsview, create, edit, delete, sync
transactionsview, create, edit, delete, categorize
accountsview, create, edit, delete
journalsview, create, post, reverse
reportsview, generate, export
settingsview, edit
integrationsview, create, edit, delete
api_keysview, create, delete
auditview
rulesview, create, edit, delete
assetsview, create, edit, delete

These permissions can be assigned individually to workspace members, allowing you to create custom access profiles. For example, a junior accountant might have transactions:view, transactions:categorize, and reports:view but not journals:post or settings:edit.

Set during registration, the account type determines the user’s primary workflow:

Account TypePurpose
BusinessCompanies managing their own crypto accounting
PracticeAudit firms and accounting practices managing client books
Tax AdviserTax-focused advisory work
IndividualSolo users managing personal crypto

Practice users (audit firms, accounting practices) have a dedicated portal for managing client relationships:

  • Practice → Clients — Manage client companies and workspaces
  • Practice → Billing — Practice-specific billing (separate from standard billing)
  • Practice → Shared — View workspaces shared with the practice

Practice users can access client workspaces without the client incurring additional charges (“no double billing” principle).

When a business grants access to an external party (auditor, accountant, regulator):

  1. Navigate to Settings → External Access
  2. Invite the external party by email
  3. Assign appropriate roles and granular permissions
  4. The external party sees the shared workspace alongside their own workspaces

Workspace sharing — auditor view

A team member’s effective permissions are the intersection of all applicable role tiers:

  • Jane has Company Role: OWNER, Workspace Role: MANAGER on “DeFi Ops” and VIEWER on “Treasury”

    • Jane can fully manage the DeFi Ops workspace but only view Treasury data
  • Bob has Company Role: VIEWER

    • Bob has read-only access to everything in the company, regardless of workspace roles