Organizations in Jozu Hub

INFO

Organizations are only available in self-hosted Jozu Hub. On Jozu Hub SaaS, every user has a personal Account where they can create public or private repositories. There is no shared organization scope on SaaS.

An Organization is a shared namespace that holds repositories owned by a group of users rather than a single account. Use organizations to group repositories by team, product line, or business unit, and to control who can pull, push, and administer those repositories.

For the conceptual definition of an organization and how it relates to Users and Repositories, see Repositories in Jozu Hub and Users in Jozu Hub.

Who can create an organization

Only System Administrators of Jozu Hub can create a new organization. Once the organization exists, the creator is made the Organization Owner and is the only person who can delete an Organization (only empty organizations can be deleted). Organization Owners can transfer ownership to any other user on the Hub.

INFO

Limiting creators of Organizations simplifies naming control in a self-hosted install where compliance, audit, and naming conventions may need to be centrally enforced. It also prevents users from creating shadow organizations.

Visibility

Organizations themselves are always public. Anyone signed in to the Hub can see that the organization exists and browse its public repositories. Organizations cannot be hidden or made private.

Repository visibility is controlled separately. Repositories inside an organization can be either public or private, regardless of the organization's visibility. A private repository is only visible to users with at least Guest rights in the organization that owns it.

User roles

Each member of an organization holds one of four roles. Roles are additive: each higher role includes the permissions of the role below it.

Role	Permissions
Guest	Visibility into private repositories and read / pull access to them. Not needed for public repositories - any signed-in user can read and pull from those.
Developer	Guest permissions, plus the ability to push ModelKits and create new repositories in the organization.
Organization Admin	Developer permissions, plus the ability to add, remove, and change roles for other members.
Organization Owner	Org Admin permissions, plus the ability to delete the organization and every repository inside it.

Transferring ownership

There is only one Org Owner per organization at any time.

Org Admins can remove themselves from an organization at any point. The remaining admins and the owner retain their existing rights.

The Org Owner cannot remove themselves directly. To leave an organization, the Owner must first promote an existing member to Owner. Because there can only be one Owner, promoting another user automatically demotes the current Owner to Admin. The newly demoted Admin can then remove themselves from the organization if they choose.