Beacon

Configure workspaces

View as Markdown

Configure workspaces

Organize teams, permissions, and modes per organization.

howto • updated 2026-03-15

Use one organization per operational entity with clear separation between technical, fiscal, and support responsibilities.

Step-by-step

  1. 11) Create baseline structure

    Define organization, owner, and operating context (test first, then live).
  2. 22) Configure team

    Invite members by role and enforce least-privilege access.
  3. 33) Validate critical access

    Confirm who can perform sensitive actions (billing, fiscal, webhooks, team management).

Minimum permission matrix

RoleRecommended access
Ownerfull management and critical approvals
Admindaily operation, fiscal/billing work, and operational investigation without ownership transfer

Functional teams such as finance or support should be mapped to the real Owner or Admin memberships based on actual operational need.

Security checklist

  1. Review active members and remove obsolete access.
  2. Enforce 2FA for profiles with critical privileges.
  3. Log role changes with auditable justification.