Skip to content

Organizations

An Avrea organization groups together users, GitHub App installations, cache settings, and billing. A user can belong to multiple organizations and switch between them from the org picker in the console.

Your account is how you sign in. An organization is a workspace you are a member of, not something you own: whoever creates one starts as its Admin, with the same rights as any Admin added later.

  • Company and personal use. Create one organization for each and switch between them from the org picker. They share no GitHub installations, settings, or billing.
  • Handing over. Add a colleague as a second Admin and set a company billing email. You cannot remove yourself, so the other Admin removes you when you leave.
  • Always one Admin. The last Admin cannot be removed or demoted.

Every member of an organization has one of three roles. Roles are hierarchical: each higher role (Admin > Billing admin > User) includes every permission of the roles below it.

RoleAdds
AdminManage org settings, installations, email domains, and members.
Billing adminView and manage billing, invoices, and payment methods.
UserRead access to workflows, jobs, logs, cache entries, and analytics.

Roles are assigned per-organization. Admins grant and change roles and remove members under Settings → Members. A role never widens repository access: everyone, Admins included, sees only the repositories they can read on GitHub.

There are two ways to bring people into an organization. Both live under Settings → Members → Invite.

From GitHub lists the people who work on your repositories on GitHub and are not members yet, with their highest permission there. Tick the people to invite, choose a role for each, and click Invite. The list shows only the people you can see through repositories you can push to on GitHub, and it needs your GitHub account linked to Avrea.

To invite someone else, enter an email address or GitHub username, choose a role, and click Invite. The default role is User.

The next time the recipient signs in to console.avrea.com with that email or GitHub account, they see an accept/decline prompt and join with the role you chose.

Add an email domain to invite everyone with a verified address in it as a User: people who already use Avrea when you add the domain, and new people when they sign up. They accept from the same prompt.

To configure domains, in the same dialog:

  1. Open Allow users with these email domains to automatically join.
  2. Pick a domain. You can add domains that match one of your own verified email addresses; a company domain you verify under SAML single sign-on joins the list too.
  3. Save.

Change a member's role afterward if they need more than read-only access.

For centralized company sign-in, automatic member provisioning, and optional enforcement on verified domains, see SAML single sign-on.

Billing is per-organization. Admins and Billing admins can see the billing page, which lists current-period usage, invoices, payment methods, billing contact emails, and tax ID.

Usage is metered per second of job run time and invoiced monthly. See Runners & Pricing for per-minute rates.

For things the console doesn't currently support (renaming or deleting an organization), reach out to support@avrea.com.