One customer, one workspace.
Every customer gets an isolated workspace with its own members, roles, subscription, feature flags and data. Users switch between the workspaces they belong to, and your app reads whichever one is active.
Your app is an organization in BuildBase. Your users sign in and work inside workspaces - one per team or customer.
You set up
In the console and the SDK
- Whether new users get a workspace automatically when they sign up
- Whether users may create more workspaces of their own
- A switcher in your app - one component, you design the button
Your users get
Inside their workspace
- Their own workspace, with its own members, plan and data
- Invite teammates and give each of them a role
- Switch between every workspace they belong to
Multi-tenancy you do not have to design
The tenant model, the switcher and the member screens are already built. You render a trigger button.
Switch in One Click
Users see every workspace they belong to, search it, create a new one and switch. You only style the button that opens it.
Teammates and Roles
Users invite teammates by email and choose what each one can do. Everything a teammate can see follows the role they were given.
A Plan per Workspace
Each workspace has its own plan, seats and limits, paid by the workspace or by someone paying for it. One team hitting a limit never blocks another team.
Ready on First Sign-in
A new user lands in a workspace straight away, with no setup step. You decide whether they can create more.
Settings Already Built
Members, billing, features and the rest open in a ready-made settings screen, so you do not build those pages.
Nothing Leaks Between Teams
Data, feature switches and settings belong to the workspace. Switching workspace switches everything your app shows.
A switcher, the member API and invitations
WorkspaceSwitcher handles search, create and switch. useSaaSWorkspaces() invites people whether or not they have an account yet, and PendingInvitations shows someone the invitations waiting for them.
import { useSaaSWorkspaces, WorkspaceSwitcher } from '@buildbase/sdk/react';
function App() {
const {
workspaces,
currentWorkspace,
createWorkspace,
switchToWorkspace,
addUser,
removeUser,
} = useSaaSWorkspaces();
return (
<nav>
<WorkspaceSwitcher
trigger={(isLoading, ws) => (
<button>{ws?.name ?? 'Select workspace'}</button>
)}
/>
</nav>
);
}import {
PendingInvitations,
useSaaSWorkspaces,
WhenPendingInvitations,
} from '@buildbase/sdk/react';
// Invite someone who may not have an account yet. The email link
// lands in your app, and the SDK shows the accept dialog.
export function InviteButton({ workspaceId }: { workspaceId: string }) {
const { inviteMember } = useSaaSWorkspaces();
return (
<button
onClick={() =>
inviteMember(workspaceId, '[email protected]', 'editor')
}
>
Invite a teammate
</button>
);
}
// An invite-only app: a new user starts with their invitations.
export function NoWorkspaceYet() {
return (
<WhenPendingInvitations fallbackComponent={<p>Ask your team for an invitation.</p>}>
<PendingInvitations />
</WhenPendingInvitations>
);
}The rules around workspaces, already decided
Modes, invitations, limits and the tricky cases between them are built and tested. You pick the settings in the console instead of designing them yourself.
Personal or Platform
Pick Personal for an app people use alone: everyone gets one workspace of their own. Pick Platform for teams, who create shared workspaces, join them and invite others. One switch in the console sets five rules at once, and you can change any of them later.
Invitations to anyone
Invite any email address, whether or not that person has an account yet. The invitation lasts 14 days and keeps a seat for them while it waits. You can resend it, at most once every five minutes, or cancel it. It even lets that one person sign up when sign-up is otherwise closed.
Limits you choose
Choose who can create workspaces, and whether everyone, only admins or no one can invite people. Then set how many workspaces one person can own, and how many members fit in one workspace.
No mix-ups when clicks collide
If an invitation is accepted twice at once, the person joins once. If you cancel an invitation just as it's accepted, only one of the two happens. Two people can never both take a workspace's last seat. And a workspace's creator and last admin can't be removed.
Every workspace in your console
Open any workspace to see its members, pending invitations, features, quotas, credits, plan, plan history and invoices. Handy when a customer asks you what happened.
Every change on your webhooks
Your other systems learn about 13 kinds of workspace change as they happen, by webhook (a message sent to your server) or as a workflow trigger. Among them: a new workspace, a member invited, added, removed or given a new role, and an invitation accepted, declined, cancelled or expired.
Works well with
Other modules for users & access.
Read more in the docs
Setup guides and reference for Multi-Tenant Workspaces.
Overview
Isolated workspaces with independent data, billing, and settings.
Managing members
Invite members, assign roles, and track seat usage.
Invitations
Invite people who have no account yet. An invitation lasts 14 days and holds a seat, you can resend or cancel it, and sign-up can be invite-only.
Mode and limits
Choose Personal or Platform, who can create workspaces and invite, the role new members get and how many fit, all in the console.
Workspace switcher
Drop-in workspace selector with search, create, and switch built in.
Settings screens
Pre-built settings for profile, members, billing, usage, features, and more.
Frequently Asked Questions
What people ask about Workspaces.
Do my users see this?
Yes. Workspaces are where your users work: each one has its own members, roles, plan and data, and users switch between the workspaces they belong to.
What is the difference between an organization and a workspace?
Your organization is your app inside BuildBase - where you set everything up in the console. Workspaces live inside it and belong to your users, usually one per team or customer.
Does every new user get a workspace?
By default, yes: one is created on their first sign-in. You also decide whether users may create more workspaces themselves.
Does each workspace pay separately?
Yes. Plans, seats, quotas and credits belong to the workspace, not to the user, so one team hitting a limit never blocks another.
Can each person have just one workspace of their own?
Yes. In Personal mode each person gets exactly one workspace, with no switcher and no invitations. That suits an app people use on their own. Platform mode gives shared workspaces that people create, join and invite others into, and switching to it needs a BuildBase plan that includes it. One switch in the console picks either, and you can change any of its rules later.
Can people invite someone who has no account yet?
Yes. You can invite any email address. The invitation lasts 14 days and holds a seat while it waits. Its link opens your app, where the person signs in or signs up and accepts, even when public sign-up is off. Admins can cancel it, or resend it once every five minutes at most.
Give every customer a workspace
Wrap your app in the provider and drop in the switcher. Members, roles and per-workspace billing are already there.