Skip to main content

Core Concepts

Entity Hierarchy

Workspace types

TypeDescription
UserWorkspacePersonal workspace — every user gets one automatically
OrgWorkspaceOrganization workspace — created when an org is created; an org can have multiple

Users switch between workspaces using the workspace switcher. The URL prefix indicates the type:

  • /p/$workspaceSlug/... — personal workspace
  • /o/$orgSlug/... — organization workspace

Roles

Team / org roles (assigned per team)

RoleDescription
SUPERADMINPlatform-level admin
OWNERFull org control, billing
ADMINUser management, template configuration
MANAGERApplication management, document review
MEMBERProcess applications
CLIENTClient user — sees only their own data and EXTERNAL comments

Permissions cascade: a user with a role on an org workspace has that role across all its teams.

Per-application roles (assigned per applicant)

RoleDescription
VIEWERRead-only access to the application
COMMENTERCan add comments
EDITORCan edit application details

Key entity relationships

EntityBelongs toNotes
OrgWorkspaceOrganization1 org → many workspaces
OrgPublicProfileOrgWorkspaceAlways 1-to-1; created automatically
TeamWorkspaceA workspace has many teams
MemberTeam + UserA user joins a team; gets a role
ApplicationWorkspace (team-scoped)Created from a template
ApplicantApplicationUp to 5 per application (PRIMARY → FIFTH)
PublicUserProfileUserA user can have multiple profiles; shared with orgs
ApplicationStatusApplicationTemplateTemplate-scoped custom statuses
DocumentDefinitionWorkspaceWorkspace-scoped; reused across templates
ApplicationDocumentApplicationActual file upload; belongs to a document slot

Comments — internal vs external

This is a fundamental business rule:

  • INTERNAL comments are visible only to org staff (OWNER, ADMIN, MANAGER, MEMBER)
  • EXTERNAL comments are visible to staff and clients

Clients never see internal comments. When adding a comment, staff must choose visibility explicitly.

See Comments & Messaging for full details.