Skip to main content

Collaborators and account access

Bobuild distinguishes people who build from people who use the live app. Mixing those up is the most common access mistake.

Builder collaborators vs app users​

CollaboratorsApp users
Where they workBuilder (builder.bobuild.com)Your app portals
PurposeDesign objects, pages, tasks, inspect dataDay-to-day work through forms and grids
AuthBobuild account invitationRecords of a login object (User login)
CredentialsKeep tightly controlledIssue per portal / role as needed

From Basic concepts: keep Builder credentials for the people who should change the app. Everyone else should work inside portals you design.

Inviting collaborators​

Collaborators are managed from your Bobuild account / organisation area (not inside a single page widget). Invite people who need to:

  • edit the data model or pages;
  • run Builder imports;
  • take snapshots or launch deployments;
  • use the SQL Console or API configuration.

When you restore a snapshot, collaborators from the source app are copied onto the restored app where applicable.

App limits​

Accounts have limits on how many apps you can keep active. Restoring a snapshot creates a new app and will fail if you are at capacity — free a slot or upgrade before restore. Plan features (scheduled tasks, SPID/CIE, and similar) may also need enabling; see Troubleshooting.

For pricing and plan details, see bobuild.com or contact us.

Practical rules​

  • Prefer one or two Builder owners plus a staging collaborator over sharing Builder login widely.
  • Give staff Operator portal accounts instead of Builder access when they only process records.
  • After a teammate leaves, remove their collaborator access and deactivate their operator record.
  • Use staging + deployments so experimental Builder work does not happen on production.