Organizations and teams
Organizations, teams, roles and invitations, and what belongs to a team.
Everything you build in Harthelm belongs to a team, and every team belongs to an organization. Roles on the organization, the team and each workspace decide what you can do.
What belongs to a team
- Its workspaces, with their landscapes, env vars and secrets.
- Its managed services: databases bound to a workspace's landscape, and standalone ones.
- Its custom domains and container registries.
- Its quota: how much CPU, memory and storage all of this may use together. See Plans and quotas.
- Its members.
The team switcher at the top of the console shows which team you are in. A team admin renames the team under Settings → General.
Organizations
An organization holds teams and their members. Joining a team makes you a member of its organization too. Cluster admins create organizations; each starts with one owner, who invites the rest.
Roles
| Role | On | Can |
|---|---|---|
| Member | organization | See the organization and its members |
| Owner | organization | Manage the organization, its members and its teams; is an admin of every team in it |
| Member | team | Create workspaces and managed services; see the team's workspaces |
| Admin | team | Also invite and remove members, change roles, add domains and registries, change team settings; is an admin of every workspace of the team |
Roles inherit downwards: an organization owner is an admin of every team, and a team admin is an admin of every workspace of the team.
Workspace roles
On each workspace, people have one of three roles:
| Role | Can |
|---|---|
| Viewer | Follow the workspace: the Run panel, logs, the files (read only), who has terminals open. No IDE, no terminal |
| Editor | Write code, use the IDE and terminals, run commands, change Git access, Sync and Run the landscape |
| Admin | Also change the workspace's settings, give roles and delete it |
Whoever creates a workspace is its admin. Every other team member is a Viewer of it until a workspace admin gives them a higher role under Workspace access on the workspace's rail. A role given there can only raise what the team already gives; see Invite members.
The workspace owner
Every workspace with a Git repository has one owner, at first its creator. Harthelm's Git proxy clones, pulls and pushes with the owner's Git connection. If the owner leaves the team, the workspace waits for a new owner and Git stops working for it until a workspace admin offers the ownership to someone with a Git connection and they accept.
Invitations
A team admin invites people by email address; an organization owner invites people to the organization. The invitation
mail links to <console>/invite/<token>, which works for 7 days. Accepting needs a sign-in with the same,
verified email address the invitation went to. Pending invitations also show in the console's top bar for the
invited person.
Someone who has signed in to Harthelm before can be added directly, found by their verified email address, without an invitation.
Leaving
Leaving a team removes your workspace roles there. Workspaces you own wait for a new owner. Leaving your last organization also deletes your Git connections.
The last owner of an organization and the last admin of a team cannot leave or be removed; make someone else owner or admin first.