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, and the upload token must be authorized for that organization and project. See Project name and publisher fields for how the fields map to namespaces.

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.

There are three separate access paths to keep in mind:

  • an organization role: Owner, Manager, or Member

  • a direct project role, such as Owner or Maintainer

  • a team-derived project role from an organization team

Being an organization member does not automatically provide release permissions for every project in the organization; a user still needs the appropriate direct project role, access through an organization team, or an upload token scoped to that project. See Organization teams for how organization teams provide project roles, and Roles and permissions for what each organization and project role can do.

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

First upload and existing project access#

An organization Owner or Manager can use an account API token to create the first project in the organization namespace. When that first upload succeeds, Sysand Index creates the project and makes the uploader a direct project Owner.

After the project exists, uploading another release requires effective project Owner or Maintainer access, or a project-scoped publishing credential. Effective project access can come from direct project membership or from an organization team with project access.

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. Some deployments, such as the test index at test.sysand.com, approve organization requests automatically; on sysand.com they are reviewed by staff.

For the step-by-step workflow, see Create an organization. After the organization exists, see Manage organization team access to set up team-based project access.

When to use an organization#

Create an organization when:

  • a project should be published under a team or company name

  • multiple people need to manage projects under the same publisher namespace

  • the publisher identity should outlive an individual user’s account

  • related projects should be discoverable under one shared namespace

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