Sharing: your organization and the world

Everything belongs to an organization. Who can see and use it is decided by two things.

In your organization

Every member sees what the organization owns. Members and owners make and change it; viewers only read.

Secrets (keys, logins, tokens) are different: they belong to the person who made them. Others in the organization can use one only if it is shared, and even then they can use it, never see it.

With everyone (public)

A Public switch at the bottom of a resource’s form makes it visible to everybody, read-only: they can open it and use it from their own resources. It is for things worth sharing widely, such as a tree, a repository or a config.

Rules that keep public things reproducible:

  • A public resource may use only public things (a public build that depends on a private repository could not be reproduced by anyone).

  • A private resource may use public ones, and its own organization’s.

  • Writing is stricter than reading: a build uploads only to a repository of its own organization. A public repository is readable by everyone and writable only by its owner.

  • A signing key is never public.

The kaji organization

The platform’s own public resources belong to the system organization, kaji. You see them as kaji/gentoo-old, kaji/fau-gentoo and kaji/server. They are read-only for you.

Names

A resource’s full name starts with its organization (cp-nginx). The lists show the short name (nginx) and put the full one in a tooltip. Names are unique within the system, so if a name is taken the form says so.