logo
AccountOrganizations
Account

Organizations (Cloud)

How SlugBase Cloud scopes data to organizations, default workspaces, members, roles, and invitations on the Team plan.

Cloud vs self-hosted: This page describes the hosted product at slugbase.app. In-app behavior shared with core is documented in the Self-hosted guides unless this page says otherwise.

What an organization is

On Cloud, bookmarks and related data are scoped to an organization (your billing and plan attach to that organization). Self-hosted SlugBase is single-tenant; Cloud adds this layer so many customers can share one deployment safely.

Your first workspace

When you first use the service with a new account, the backend ensures you belong to at least one organization. If you had none, it creates one (a Free plan organization with a default name derived from your email) and attaches you as owner. The session then uses that organization as the current workspace so API calls and the UI see the right data.

If your session has no current organization but you already belong to orgs, the client can select the first membership returned by the API so you land in a valid workspace.

Members and roles

Each organization has members with a role (listed with join time and basic profile fields for people you are allowed to see). Owners and admins can invite users on eligible plans (see Collaboration).

Invitations (Team plan)

Creating invitations is enforced server-side: only owner or admin may invite, and the organization must be on the Team plan. If the plan is not Team, you see an error indicating you need to upgrade to invite members. Seat limits apply when adding people (see Plans and limits and Billing).

Accepting an organization invitation

You must be signed in before acceptance can succeed. The address on your account must match the email the invitation was sent to—otherwise acceptance is blocked. When you complete the flow, the server checks the invitation token you were given (for example from the email or the page that opened after you followed a link).

There is no separate product URL path documented in the open app for org invites; follow the link or instructions in the invitation email (or from whoever invited you). Create an account or sign in using that same email, then finish acceptance as the app or email directs.

Use the invited email

Open the invitation link or follow instructions from the inviter. If you need an account, sign up with the same email the invitation was sent to. If you already have an account, sign in with that email.

Stay signed in

Complete acceptance while logged in as that user. If you are on the wrong account or a different email, switch accounts or fix the email first.

Complete acceptance

Finish the steps the product shows after you follow the link. The server validates your token and adds you to the organization when everything matches.

If something goes wrong, typical cases include: invitation not found, already used (or cancelled), expired, wrong email (the invite was sent to a different address than your signed-in account), or no spare seats on the Team plan—in that case, ask an owner or admin to add seats in Billing, then try again.

Multiple organizations

The server supports listing organizations you belong to and creating additional named organizations. Plan and billing are per organization. Day-to-day product flows assume a current organization in your session; the client and server keep that selection in sync when you use the app.