Skip to content
Browse help

Account and access

Roles, seats, and permissions.

Access has four layers: your seat class, a separate role in each room, any record-level role or grant, and the current record state. Passing one layer never skips the next.

Roles are assigned separately for each business. Being a Billing admin in Acme does not make you a Billing admin in GNA, and being a Shop admin does not grant Documents or Books access. Links between rooms and Wren follow the same intersection of permissions.

On the team page, each role menu is labelled with a short code for its area: WORK is Work, LOOP is Chat messages, TIES is Chat customers and contacts, CREW is Team, TABS is Books, BILL is Billing, PACT is Documents, RSVP is Bookings, and HIVE is Shop. Perch and Alder use a few different room names (in Perch, Shop is nest and Documents is contracts); the roles are the same.

Seat class comes first

Full seat

What it enables
Can receive any role supported by a room that is turned on, and is intended for people who operate, approve, manage, or configure the business.
Important limits
The seat class is only a ceiling. The person's role in each room and record-level access still decide what they can see and change.

Light seat

What it enables
Assigned work and self-service pages. Current active light grants are Work Member, Books (TABS) Employee, Team (CREW) Employee, Chat messages (LOOP) Agent, Chat customers (TIES) Viewer, and Shop (HIVE) Cashier or Technician.
Important limits
No light role is currently available for Billing, Documents, or Bookings. Light users cannot be granted an admin, finance, or configuration role.

External actor

What it enables
Uses a purpose-specific portal, guest, or token flow, such as someone signing a document, a public booker on a booking link, a Shop customer or vendor link, or a Work project guest.
Important limits
Not an employee seat. The portal, link, token, or guest membership permits only its named external purpose and never grants general access to your workspace.

A new full-seat invite asks for an access level: member (the default) grants the day-to-day working role in each room, with no settings, billing, or team management; admin grants the admin role in each room. Either can be adjusted room by room from the team page afterward. A new light seat receives only the default self-service roles; in Shop that default is Cashier, which an admin can change to Technician.

How role inheritance works

Owner

What it enables
The target top tier for people ultimately responsible for one business. In rooms that have moved to the new roles it includes the Admin and Member baseline.
Important limits
Not a platform super-admin, and it does not carry to another business or another room. Several older access checks are still migrating; use the room tables below before assigning Owner.

Admin

What it enables
Includes the room's standard operational baseline plus that room's settings and management controls.
Important limits
Does not inherit a role in another room. Some private or sensitive records still require a matching object grant or field policy.

Member

What it enables
The room's standard signed-in work for records assigned or visible to that person.
Important limits
Does not inherit admin settings, exports, approvals, or sensitive fields unless the room grants them separately.

Specialist

What it enables
A member-level job role such as Shop Cashier, Shop Technician, or Chat Agent, with a deliberately focused set of pages.
Important limits
Specialist does not mean admin. Access outside that job remains closed unless another explicit grant applies.

Shop (HIVE): shop-floor roles

Shop also applies the business's enabled capabilities, so a role does not make a disabled rental, repair, or POS page appear.

Owner / Admin / Super admin

What it enables
Full Shop operation: catalog and inventory administration, customers, proposals, purchasing, vendors, reports, settings, consignment, repair, sales, trials, rentals, web orders, shipping, discounts, and one-sale tax exemptions.
Important limits
Limited to this business and its enabled Shop capabilities. Financial or agreement context from another room still requires access to that room.

Cashier

What it enables
Counter work: dashboard, catalog lookup, scan, customers, manual stock adjustments, register and sales, charges and payment links, trials, rentals, web orders, shipping, and the shared due-date queue.
Important limits
No repair bench, inventory administration, procurement, vendors, reports, or settings. Cannot authorize arbitrary register discounts or one-sale tax exemptions. For assisted phone orders, an admin may delegate line discounts and shipping waivers in Shop settings; both are off by default.

Technician

What it enables
Bench work: dashboard, catalog lookup, scan, manual stock adjustments, repair tickets, and the shared due-date queue.
Important limits
No counter sales or payments, customers, trials, rentals, web orders, shipping, procurement, reports, or settings. Cannot authorize discounts or tax exemptions.

Member

What it enables
Basic inventory support: dashboard, catalog lookup, scan, customers, and manual stock adjustments.
Important limits
No register, payments, repair bench, trials, rentals, web orders, procurement administration, reports, settings, discounts, or tax overrides.

Work (WORK): business roles and project roles

Admin / Super admin

What it enables
Standard Work access plus the business's workflows, forms, integrations, reports, client sign-offs, audit activity, and administrative settings. Admins can resolve visibility inside their own business while operating the workspace.
Important limits
The bypass stays inside this business. Cross-business reads and writes still require membership in the other business, and every write names one business.

Owner (migration in progress)

What it enables
Owner-level project visibility and administration on Work pages that use the standardized role policy.
Important limits
Several older Work settings and administration gates still check Admin or Super admin literally. Use Admin for a person who needs dependable business-wide administration until that migration is complete.

Member

What it enables
Daily focus, planner, tasks, boards, projects, teams, labels, schedules, and personal settings, subject to assignment and project or team visibility.
Important limits
Does not see every private project. Access needs assignment or watch access, explicit project membership, qualifying team membership, or business-wide visibility.

Accounting

What it enables
Work finance and review pages for each business where the person has the Work accounting grant, including scoped receivables actions such as sending invoices and recording offline payments.
Important limits
Not a general Work admin. Invoice creation and voiding and bank-link administration remain admin-only, and project visibility rules still apply.

Project / Team Owner, Admin, or Member

What it enables
Controls management inside that exact project or team. Owners and admins manage its membership and structure; members participate in work they can see.
Important limits
An object role does not grant business admin rights or access to another project or team.

Billing (BILL): receivables and billing

Owner / Admin / Super admin

What it enables
Full billing workspace plus settings and admin-only proposal and invoice lifecycle controls, including draft editing and send, void, or delete controls when state permits.
Important limits
Paid, voided, or otherwise locked records have additional state rules. A link from Work or Shop supplies context, not authority.

Accounting

What it enables
Billing workspace and the business's billing export for day-to-day financial review.
Important limits
Does not inherit admin settings or admin-only proposal and invoice lifecycle controls merely because it can read financial data.

Member

What it enables
Standard billing workspace and time-entry participation available to a signed-in Billing user.
Important limits
No admin settings or admin-only proposal and invoice mutation controls. Record state, engagement collaboration, and assignment can narrow actions further.

Documents (PACT): documents and signatures

Admin

What it enables
All of the business's documents, including restricted documents, plus template administration, approvals, settings, packets, and export.
Important limits
Signer identity and signing authority still come from the signing step. A link from Work or Shop does not bypass Documents access.

Owner (migration in progress)

What it enables
All of the business's documents, including restricted documents, and ordinary document, template, packet, and contact work.
Important limits
Documents' older settings navigation and export check still require Admin (or a previously stored Super admin). Use Admin for full administration until those checks migrate.

Member

What it enables
Open documents visible to the whole business, restricted documents they created, and restricted documents with an active user or email grant. Members can manage document work they are authorized to open.
Important limits
Cannot see every restricted document or use admin settings, approval, and export controls.

Legacy Super admin

What it enables
Previously stored Documents Super admin rows keep the current Admin-level settings and export access.
Important limits
Not a role an admin can newly assign.

Token signer

What it enables
Review and sign the specific document the signing link is addressed to.
Important limits
Not a member and cannot browse the business's Documents room or other documents.

Chat messages (LOOP): internal and external communication

Admin

What it enables
External inbox and sending, contacts, templates, voice when enabled, internal chat, messaging and provider settings, and export.
Important limits
Message consent, channel availability, exact thread access, and space membership still apply.

Owner (migration in progress)

What it enables
Customer inbox and sending, contacts, templates, voice when enabled, internal chat, and chat administration.
Important limits
Several older provider, credit, event-operations, and export gates still check Admin literally. Use Admin when those controls are required.

Agent

What it enables
Operate the customer inbox, send messages, manage contacts and templates, use voice when enabled, and participate in internal chat.
Important limits
No export or provider administration. A light-seat Agent cannot create or curate space context even though it can use existing messaging and chat pages.

Viewer

What it enables
Read-only review of customer threads where the Chat review page is available.
Important limits
Cannot compose customer messages, operate the queue, use internal chat, or change messaging configuration.

Member

What it enables
Internal direct messages and existing chat-space participation.
Important limits
No customer-message sending. Some full-seat navigation still exposes the external queue, but its write actions require Agent, Owner, or Admin.

Space Owner / Admin / Member

What it enables
Controls one internal space: owners and admins manage its membership and settings; members participate.
Important limits
A space role does not grant Chat administration or external-inbox authority.

Chat customers (TIES): customer relationships

Admin / Super admin

What it enables
Full customer-record operation plus custom fields, settings, snapshots, administrative automation, and export.
Important limits
Linked Work, Shop, and Chat message history is still filtered by the viewer's permission in each room.

Owner (migration in progress)

What it enables
Normal customer work across customers, contacts, jobs, leads, campaigns, tags, and relationship activity.
Important limits
Older custom-field, settings, snapshot, automation, and export gates still require Admin. Use Admin for full customer-record administration.

Member / Staff / Agent

What it enables
Create and update customers, contacts, jobs, leads, campaigns, tags, and normal relationship activity.
Important limits
No admin settings, custom-field administration, snapshots, or export.

Viewer

What it enables
Read-only customer, reporting, and conversation-history access. Viewing a conversation or marking a notification read may advance only that viewer's personal read state. This is the Chat customers role available to a light seat.
Important limits
Cannot create, update, delete, send, merge, convert, save views, or change customer-record configuration. Unknown roles also fail the same server-side write checks.

Books (TABS): expenses and accounts payable

Admin

What it enables
All expenses and vendor bills, approvals, payment and reconciliation work, vendors, reports, settings, exports, and admin-only void or override controls.
Important limits
Approval separation-of-duties and document lifecycle rules can still prevent an action on the admin's own submission.

Owner (migration in progress)

What it enables
The target top-level Books role can be stored.
Important limits
Books navigation and privilege checks still use the older Admin label, so Owner does not yet provide dependable admin access. Use Admin until migration is complete.

Accounting

What it enables
All of the business's expenses and bills, approvals, payment scheduling and mark-paid work, reconciliation, vendors, reports, export, and intake.
Important limits
No business settings or admin-only void and override controls. Self-approval is allowed only under configured fallback rules.

Manager

What it enables
Enter spend, see operational dashboard, vendors, and reports, and approve other people's expenses and bills in scope.
Important limits
Cannot pay or reconcile bills, change Books settings, use admin overrides, or normally approve their own submission. The main expense list remains limited to their own spend.

Employee

What it enables
Enter, import, submit, and follow their own expenses and vendor bills; use receipt intake and assigned cards.
Important limits
Cannot see everyone else's spend, approve, pay, reconcile, report across the business, or change settings.

Member (migration in progress)

What it enables
The target standard self-service role can be stored.
Important limits
Books navigation and several scope checks still expect Employee. Use Employee for dependable self-service until migration is complete.

Team (CREW): people and sensitive fields

Tenant admin / business-scoped Super admin

What it enables
The business's roster, hiring, offers, onboarding, employee records, time and time-off administration, documents, reports, imports, data, and HR settings.
Important limits
Only inside the active business. A business-scoped Super admin is treated as Tenant admin; platform-wide support authority is separate.

Owner (migration in progress)

What it enables
The target top-level Team role can be stored.
Important limits
Team's HR administration checks still use Tenant admin. Use Tenant admin for dependable HR administration until migration is complete.

Admin (migration in progress)

What it enables
The target Team admin label can be stored.
Important limits
Team's HR administration checks still use Tenant admin. Use Tenant admin until migration is complete.

Read-only admin

What it enables
Broad HR reporting and employee visibility, including sensitive fields, inside the active business without ordinary employee-edit authority.
Important limits
No ordinary employee edits or HR write actions, and no access to another business. An active business context is required; a legacy assignment without one is denied. The role is planned to become Admin plus a viewer modifier for one business.

Manager

What it enables
Own HR self-service plus direct-report directory, documents, time, time-off review, positions, and team work. Direct-report compensation and date of birth use hold-to-reveal.
Important limits
Limited to self and the management chain. Direct-report bank and SSN fields stay hidden; no business HR settings, offers, onboarding administration, imports, or exports.

Employee

What it enables
Own profile, tasks, time, time off, pay preview, and employee documents.
Important limits
Cannot browse or edit other employees or access the business's HR administration.

Member (migration in progress)

What it enables
The target Team self-service role can be stored.
Important limits
Team's self and manager visibility checks still expect Employee or Manager. Use Employee for dependable self-service until migration is complete.

Linked Team panels and Wren never expose an individual pay rate. Even for a compensation-authorized role, aggregate labor cost and covered hours are withheld when fewer than three distinct employees contribute.

Bookings (RSVP): bookable resources and appointments

Admin

What it enables
Create and manage people, room, and equipment resources; booking links and availability; pending booking decisions; scheduling defaults; calendar and meeting integrations; and export.
Important limits
Limited to this business. Public customers can only use the booking or cancellation token they receive.

Owner (migration in progress)

What it enables
Business schedule review and management of booking links, availability, and pending requests for resources owned by that user.
Important limits
Bookings' older admin and export checks still require Admin (or a previously stored Super admin). Use Admin for business-wide resource creation and settings.

Member

What it enables
Review the business schedule and manage booking links, availability, and pending requests for resources assigned to that user.
Important limits
Cannot create resources for the business, change scheduling defaults, administer another person's resource, or export the business's data.

Legacy Super admin

What it enables
Previously stored Bookings Super admin rows keep the current Admin-level scheduling and export access.
Important limits
Not a role an admin can newly assign.

Public booker

What it enables
Use one public booking link and the resulting cancellation or calendar links.
Important limits
Not a seat or member and cannot browse the business schedule.

Links between rooms never widen a role

A Shop order can point to an invoice in Billing, an agreement in Documents, a cost in Books, a time entry in Team, and a conversation and customer record in Chat. Each room still checks the role and exact record before returning its part. If one source is outside your permission, that source is withheld rather than replaced with a nearby record.

Wren receives that same authorized intersection. Read visibility does not give Wren action authority; a supported change is confirmed and checked again by the room that holds the record when it runs. See What happens between rooms and Working across multiple businesses for how rooms link and how businesses stay separate.