Organization
The top-level workspace for your company. It holds every member, every team and every Artifact and Kit your people create, and it is where your plan and settings live.
See how to customize itHubBound Org & Teams mirrors your company: one organization, its teams and three roles, so every team gets exactly the Kits it needs.
Org & Teams is the part of HubBound that models your company: one organization that owns your members, Artifacts and Kits, teams that group people the way they actually work, and three roles that decide who can change what. It is how HubBound knows which AI standard belongs on which developer's machine.
The top-level workspace for your company. It holds every member, every team and every Artifact and Kit your people create, and it is where your plan and settings live.
See how to customize itGroups of people inside the organization, shaped like your real org chart: Frontend, Platform, Data. A team is the most common target for a distribution.
See the Teams screenEvery person in the organization. Each member has one organization role, belongs to the teams they work in, and receives what is distributed to those teams and to the whole organization.
See how invitations workEvery Artifact and Kit also has a visibility. It can only be raised, from Private to Organization to Public, never lowered.
Visible only to its owner: the place to draft before anything is shared.
Visible to every member of your organization, and to no one outside it.
Listed on the public Marketplace, where anyone can find and install it.
HubBound has three organization roles: Org Admin, Team Admin and Member. Org Admins run the whole organization, Team Admins run teams and decide what those teams receive, and Members use what is distributed to them, with no admin screens to learn.
| Capability | Org Admin | Team Admin | Member |
|---|---|---|---|
| Use the Kits and Artifacts distributed to them | Yes | Yes | Yes |
| Create teams | Yes | Yes | No |
| Invite people and manage team members | Yes | Yes | No |
| Distribute a Kit or Artifact to a team | Yes | Yes | No |
| Distribute to the whole organization | Yes | No | No |
| Delete a team | Yes | No | No |
| Grant or revoke Org Admin | Yes | No | No |
| Customize the organization's name, icon and color | Yes | No | No |
| Open organization Settings | Yes | No | No |
Org Admin is granted or revoked in Settings, Members, with the Organization Admin toggle. Inside each team, people are also labelled Admin or User in that team's member list.
In HubBound, an Org Admin customizes the organization from Settings, General: its company name, a square icon and a brand color. The color becomes HubBound's primary color for every member of the organization, and a live preview shows where it lands before anything is saved. The same page decides which usage metrics the organization reports.
The company name and a square icon (at least 256×256 pixels) identify your organization in HubBound's navigation, so every member knows whose workspace they are in.
Pick any color or one of eight presets. It recolors navigation, primary actions and badges for every member, while charts keep their fixed palette so data reads the same everywhere. HubBound warns you when a color has low contrast against its text.
Two switches decide whether HubBound collects usage metrics from the agents running in your organization and from GitHub. On some plans a switch is fixed and marked “Not adjustable on your current plan”.
Illustrative sample: pick one of the eight presets to see the preview change. The layout mirrors Settings, General in HubBound.
In HubBound, an Org Admin or Team Admin creates a team from the Teams screen in one step: give it a name and it appears under Your Teams. Every team then has two tabs: Members, to search, invite and remove people, and Distributions, the list of every Kit and Artifact that team receives.
Illustrative sample data. Team, member, Kit and Artifact names are for illustration only. The layout mirrors HubBound's Teams screen.
HubBound invites people to a team in bulk: an Org Admin or Team Admin adds each work email as a chip, reviews the list and sends every invitation in one step. Each address gets its own result, so one bad email never blocks the rest of the batch.
Add as many addresses as you need before sending. A repeated email is caught before anything goes out.
A batch can partly succeed, and HubBound reports how many invitations were sent and how many failed. People already in your organization join the team directly; everyone else receives an email invitation.
Your organization pays per seat, with a minimum of 5, and teams are unlimited on Core. When the seats you pay for run out, the Invite button says “No seats left” instead of failing halfway.
See the price per seatIllustrative sample. The dialog mirrors HubBound's Invite Users window; the addresses are placeholders.
In HubBound, a Kit or a single Artifact reaches people through a distribution: an admin opens Distribute from its action menu and makes three choices, the target, the rule and the version. Team distributions then appear in that team's Distributions tab, and organization-wide ones in Settings, Distributions.
Illustrative sample. The dialog mirrors HubBound's Distribute window; Kit, team and version are for illustration only.
After a distribution is saved, HubBound keeps it in effect on its own: the HubBound Runtime installs mandatory Kits on every member's machine, pinned versions stay put, and admins see and change every distribution from one list. Nobody has to send a setup guide again.
Team distributions are listed in the team's Distributions tab, organization-wide ones in Settings, Distributions. Each row shows its rule and the version it follows.
The HubBound Runtime syncs in the background and installs every mandatory distribution. Optional ones wait until a member chooses to install them.
A distribution set to Always latest moves to each new version on the next sync. A pinned one stays on its version until an admin changes it.
An admin removes the distribution from the same list, and the Kit stops being distributed to that team or to the organization.
Each piece of HubBound builds on the others. Pick where you want to go next.
See how HubBound models your organization, your teams and their roles, and gets the right Kit onto every machine.