Choose how to share your work
You can work alone on Pillion or give other people access to a repository. A personal repository belongs to your user account. An organization provides shared ownership for a group, such as a company or an open-source project.
For a small project you own, adding a collaborator in repository Settings → Collaborators may be enough. Use an organization when the group should own the repositories and manage access together, especially across several repositories.
Giving someone access lets them use their own account and credentials. You do not need to share your sign-in link, access token or SSH private key.
Create an organization
An organization owns shared repositories and groups people into teams. Your user account remains separate and can belong to multiple organizations.
Open New organization, choose a name and create it. Organization owners manage membership, settings and all repositories owned by the organization.
Invite members
Open the organization’s People page to invite people. Give ordinary contributors the member role; make someone an organization owner only when they need to manage the whole organization.
Membership and repository access are separate. The organization’s base permission gives every member a role on all its repositories. New organizations start with no base permission.
Grant access through teams
A team groups members who need similar access. For example, a documentation team might need write access to the docs repository and read access to the application. Create it from the organization’s Teams page, add members and grant a role on each repository it needs. Teams cannot contain other teams.
A repository role describes what someone may do there. Start with the least authority that lets them do their work:
- Read: read and clone the repository.
- Triage: help manage issues and pull requests without pushing code.
- Write: contribute code and collaborate on changes.
- Maintain: manage repository work with more authority than write access.
- Admin: manage repository settings and access.
For one-off access, add a collaborator in the repository’s Settings → Collaborators. Someone with direct access who is not an organization member is an outside collaborator; base permission does not apply to them.
Single sign-on
Single sign-on, or SSO, lets an organization require a sign-in through its own identity service, such as a workplace login. Pillion uses the OIDC protocol for this connection. An organization owner configures it in settings.
When SSO is required, follow the organization’s sign-in flow before accessing its repositories. Signing in to Pillion alone does not satisfy that requirement. If you are a member, ask an organization owner for help with the workplace account you should use.
If a token cannot access an SSO-protected repository, complete the organization’s SSO flow and check the token’s SSO authorization in Access tokens, along with its owner, permissions and selected repositories.
Manage shared settings
Organization settings hold shared secrets, attached runners, rulesets, allowed AI providers and billing. Repository settings control the individual repository. Organization rulesets apply alongside repository rulesets.
Open the organization’s billing settings to check the plan, storage and hosted CI usage. Current allowances and plan differences are listed on Pricing. For CI setup, continue to Workflows and runners.