The org's data, in the org's database.

An organization gets its own database, apart from any member's. Members sign in with their own Bazaar accounts, access is granted per collection, and the data stays when people leave.

Read the organizations docs Bazaar for teams

Acme Studio

updates · rota · kit

Ana admin

Ben updates: read · write

Dan removed · no access

OWNED BY THE ORG Its own database Org data sits in the organization's account, not with whoever built the app or any member.

MEMBERS Their own accounts Members sign in as themselves. Remove someone from the org and their access ends at once.

ACCESS Granted per collection Nobody gets implicit access, admins included. Grant read or write to the org, a team or a group.

Same API, different owner.

A context points the SDK at the org's database. Collections, files and grants work as they do for a user.

// the org's database, not a member's
const org = await bzr.createContext({ ownerId: orgId })
const updates = org.collection("updates")

// every member can read and post
await org.permissions.create({
  collectionName: "updates",
  granteeType: GranteeType.ORG,
  granteeId: orgId,
  types: [PermissionType.READ, PermissionType.INSERT],
})

Teams inside the org List the user's orgs and teams, and grant to one team instead of the whole org.

Managed on Bazaar Orgs, members and admins are managed on Bazaar. Your app opens the management popup when a user needs it.

The data outlives the builder Whoever built the app can leave. The app and the data keep working.

What organizations don't cover.

A free plan An organization needs a Team plan or higher. Business adds per-member space and a 30-day audit log.

Setup by members Only admins create collections and grants in org data, so an admin has to open your app first.

SSO, not provisioning SAML SSO is available on Enterprise. SCIM provisioning isn't built: admins add and remove members.

OTHER WINDOWS