Organizations
Organizations are the core multi-tenant boundary in NuxtBase.
The template does not treat “team” as a vague UI label. It has a concrete organization model with:
- a current active organization on the session
- organization-scoped membership and roles
- invitations sent by managers
- optional sub-groups called teams
- organization-aware permission checks on both client and server
Reading Order
Section titled “Reading Order” Members & Roles Understand owner, admin, and member behavior in the shipped product.
Invitations See how invites are created, resent, canceled, and accepted.
Teams Use optional sub-groups inside an organization for smaller working groups.
What This Section Covers
Section titled “What This Section Covers”- organization creation and active workspace selection
- role-aware access boundaries
- invitation and acceptance flows
- teams as sub-groups inside an organization
- organization-scoped product behavior
First Questions To Answer
Section titled “First Questions To Answer”Before changing this area, decide:
- what counts as a workspace in your product
- which roles are required at launch
- how invitations should behave
- what data must always stay organization-scoped
The Default Behavior
Section titled “The Default Behavior”Some organization behavior exists immediately, even on a fresh install:
- a newly created user gets a default personal organization
- that user becomes the
owner - the session stores an
activeOrganizationId - protected product flows assume an active organization exists
This is why organizations are not an add-on module in NuxtBase. They are part of the base product model.
Product Risk
Section titled “Product Risk”Multi-tenant logic touches routing, permissions, billing, and admin operations. Change it carefully and keep those systems aligned.