Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Index Organizations

Sysand Index organizations are shared publisher namespaces for team-owned projects. They let a project be published under an organization name instead of under an individual user’s username, while still keeping membership and release permissions explicit.

Organizations Are Publisher Namespaces

Every project on Sysand Index belongs to a namespace. A namespace is either a user or an organization, and usernames and organization names share one global namespace.

For example, if an organization named sensmetry owns a project named fancy-stuff.teapots, the project identifier is:

sensmetry/fancy-stuff.teapots

The sensmetry part is the publisher namespace. It must already exist on Sysand Index before a package can be uploaded under that publisher.

For the exact identifier rules and normalization behavior, see Project identifiers.

Relationship To .project.json

Packages uploaded to Sysand Index include a .project.json file with a human-readable publisher field and name field. During upload, those fields are normalized into the publisher namespace and project name used by the index.

For an organization-owned project, the normalized publisher value must match the organization namespace. For example, publisher: "Sensmetry" normalizes to sensmetry, so it can publish into the sensmetry organization namespace when the upload token is authorized for that organization and project.

Use an organization name as the publisher when the package should belong to a team, company, working group, or other shared identity. Use a personal username as the publisher when the project is owned by an individual account.

Organization Membership Is Not Project Membership

Organization roles control access to the organization itself. Project roles control access to a specific project.

Organization owners can manage the organization, its members, invitations, settings, and deletion. Organization managers can update organization profile details and manage organization projects.

Project owners and maintainers control project-level operations such as release uploads, project tokens, trusted publishers, and project membership. Being an organization member does not automatically grant release permissions for every project in the organization; a user still needs the appropriate project role or an upload token scoped to that project.

This separation lets an organization provide a stable publisher namespace while individual projects keep their own maintainers, tokens, and audit history.

Organization Requests

New organizations start as requests because organization names reserve publisher namespaces. Sysand Index checks that the requested name is not already used by a user or another organization.

After a request is approved, the namespace is created and the requester becomes an organization owner. On test deployments, organization requests may be approved automatically.

For the step-by-step workflow, see Create an organization.

When to Use an Organization

Create an organization when:

Use a personal namespace when the project is personal, experimental, or not intended to represent a shared publisher identity.