Organizations

What is an organization?

An organization is your workspace: it owns the projects, the sites, the domains, the servers and the subscription. Everything you see in the console belongs to the active organization, which you switch from the selector at the top of the sidebar. One account can belong to several organizations, and create new ones from that same selector.

The tabs on the page

The Organization page is split into five tabs, four of them owner-only:

• Members, the list of members and invitations. Visible to everyone.
• GitHub, the installation that gives Pierrr access to your repositories.
• Docker repo, where Pierrr pushes the images it builds.
• Permissions, the read-only matrix of what each role can do.
• Settings, the profile picture, the organization name and the sensitive actions.

Members and roles

The Members tab lists members and their role. Access control decides what each of them can do:

• Owner, full control: billing, members, GitHub connection, image registry, server enrollment and deleting the organization.
• Maintainer, creates and manages projects, containers and domains, opens the databases and restarts servers. No billing, no member management, no enrolling new servers.
• Developer, operates existing containers and binds an already verified domain, without creating or changing a project or a domain, and without database access.
• Billing, access to billing only (plans, invoices, affiliate program), with no view of the infrastructure.

Inviting a member

Invite a teammate by email and give them a role. Until they accept, their invitation sits in the pending invitations list, where you can resend or revoke it. A member can be removed, or have their role changed, at any time by an Owner.

GitHub connection

From the GitHub tab, install Pierrr's GitHub App on the organization or account that hosts your repositories. That is what lets Pierrr read your code, list branches and trigger builds. Once connected, your repositories become selectable when creating containers. Picking which repositories are shared happens on the GitHub side, and a button resyncs the list after a change.

If the installation is removed or suspended on the GitHub side, the tab says so and offers to reconnect it: without it, no deployment from your repositories is possible.

Image registry

The Docker repo tab decides where the images Pierrr builds for your containers end up. Two targets:

• Pierrr (hosted), images are pushed into Pierrr's own space. This is the default, included from the Free plan.
• Your own GitHub registry, Pierrr builds the image then pushes it to the account or organization you name, using a GitHub token with read and write rights on packages. Paid plans only.

On the Free plan the Pierrr option is enforced. The token you provide is stored encrypted and never shown again: leave the field empty to keep it, paste a new one to replace it.

Permission matrix

The Permissions tab shows, capability by capability, what each role can do. It is a read-only reference: it cannot be edited, it is there to help you pick the right role before sending an invitation.

Profile picture

The Settings tab holds a “Profile picture” card, above the name field. The owner picks an image there in PNG, JPEG, WebP or GIF, up to 5 MB. There is no cropping to do: Pierrr automatically takes a centred square, resizes it to 256 pixels a side and re-encodes it to WebP. A photo of several megabytes comes down to a few kilobytes, and EXIF metadata, including the location of a picture taken on a phone, is stripped during encoding.

Changing the picture replaces the previous one, which is deleted from storage right away: no orphan image is left behind. The “Remove” button deletes the picture the same way.

Without a picture, the organization shows its initials, up to two characters, on a coloured badge. The colour is derived from the name: it stays the same from one visit to the next and differs from one organization to another, which is often enough to tell them apart at a glance.

The picture is reused everywhere the organization is cited: the organization switcher at the top of the sidebar, including when it is collapsed, the Organization page header, the list of invitations you received, where it shows which organization is inviting you, and the platform admin screens.

Renaming the organization

The organization name is changed from the Settings tab. Careful, it is not a mere label: the organization identifier is derived from it, and that identifier names your containers and your Pierrr subdomains.

A confirmation dialog spells out the consequences before applying: containers are recreated, which briefly takes your applications down, and Pierrr subdomains built on the old identifier stop working. Your custom domains and your data are not affected.

Suspending and reactivating

Still in Settings, the danger zone can pause an organization: access is cut until you reactivate it, which you can do whenever you want. Nothing is deleted in the meantime.

Your primary organization is the exception: it can be neither suspended nor deleted.

Deleting the organization

An Owner can request the deletion of the organization, with an optional reason. The request goes to the Pierrr team, who validate it: in the meantime the organization is suspended and a banner recalls the state, with the date of the request. Deletion destroys projects, domains and associated data, irreversibly.