Skip to main content

Documentation Index

Fetch the complete documentation index at: https://buildpixel.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

An organization is the top-level container in BuildPixel. Every project, build, and member belongs to exactly one org. You can be a member of multiple orgs.

​
What an org owns

  • Source control credentials — one GitHub installation and / or one Perforce server config per org.
  • Members — invited at the org level, scoped by role.
  • Billing — usage rolls up at org scope.
  • Projects — every project is created inside an org.

​
Settings you can edit

In Settings → Organization:
  • Name — display name shown in the dashboard.
  • Slug — short, URL-safe identifier. Pick something stable; it appears in webhook paths.

​
Inviting teammates

From Settings → Members → Invite:
  1. Enter the person’s email and pick a role (see Roles & permissions).
  2. They get an email with a join link.
  3. They sign up (or sign in) and land in the org with the role you assigned.
Default role is member.

​
Creating additional orgs

Use the org switcher in the dashboard sidebar. Common reasons to have multiple orgs:
  • Separate billing — multiple games on separate budgets.
  • Separate GitHub installations — BuildPixel allows one GitHub installation per org.
  • Compliance / isolation — strict access boundaries between projects or clients.
If you just have multiple games, one org with multiple projects works fine and is easier to manage. Don’t create extra orgs unless you have a real reason.