Organizations & multi-tenancy

If your product is used by companies rather than lone individuals, you need more than user accounts. A customer signs up, creates their workspace, invites their teammates, and decides who can do what — and no customer should ever see another customer's data. Pikku Studio Cloud apps get this as a built-in capability: organizations, with invitations, roles, and clean separation between tenants.

Labeled diagram: two boxes side by side, "Acme Inc." and "Blue Bakery", each containing its own members and data, with a wall between them. Caption: "Each organization's people and data are theirs alone."

What your users get

• Workspaces of their own. A customer creates an organization and it becomes their home in your product.
• Invitations. They invite teammates by email; invitees land in the right organization with the right access.
• Roles. Owners, admins, members — who can invite, who can change settings, who can only view.

Example: you build a project tracker. Acme Inc. signs up, invites five teammates, and manages their projects — while Blue Bakery does the same in their own workspace, never seeing Acme's data.

Multi-tenancy — the separation underneath

"Multi-tenancy" is the plumbing that makes this safe: every piece of data in your app belongs to an organization, and every function checks that boundary. It's not something you bolt on later with hand-written database rules — it's how the app is structured from the first day, so a missed check can't quietly leak one customer's data to another.

This page is about organizations inside your product — your customers' teams. Your own Pikku Studio Cloud workspace has its own team management, described in Team & members.

Where to go next

• Users — how individual people sign in.
• Emails — the invitation emails your app sends.
• Team & members — your Pikku Studio Cloud team, as opposed to teams in your product.