Members and invitations
Last updated
An organisation in Hetscale has members: its owner and the admins they invite, and on Team also viewers and operators. Members and invitations are managed on the panel, and every plan has seats for them.
Where do I manage members?
Account → Members lists the members with their role and when they joined, and the open invitations under them.
How do seats count?
The members and the open invitations count. Starter has 2 seats, Growth 3 and Pro 5; Team has no limit; an organisation without a plan, in Observe, has 2. Invite is off once every seat is taken.
How do I invite someone?
The owner or an admin chooses Invite and enters an address. Hetscale mails a link that works for 7 days.
- An address has one open invitation. Send again mails a new link, and the earlier one stops working; Revoke ends it and frees its seat.
- An organisation sends at most 10 invitation mails in 24 hours.
- An address whose mail bounced or was marked as spam cannot be invited.
- The mail is in the invitee’s language when they have an account, otherwise in the inviter’s.
How does someone join?
The link asks them to sign in, or to sign up with the address filled in; GitHub and Google work too. Only an account with the invited address can join. The link verifies that address, so no separate verification mail is sent.
The page names the organisation, who invited, the role and the expiry, with Join and Decline. An account with another address is told the invitation went elsewhere, and can sign out to open the link again. A used, declined, revoked or expired link opens nothing.
What can the owner and the admins do?
An organisation has one owner. Only the owner opens Billing, and only the owner can make an admin the owner, with Make owner; the owner then becomes an admin. Admins do everything else, including the organisation’s profile and its members. On Team, a member can also be a viewer or an operator (below).
What do the roles on Team allow?
On Team, an invitation names the role, viewer by default. The owner or an admin changes a member’s role with Change role on the member’s row. Nobody changes their own role, and the owner’s passes only with Make owner.
Each role can do everything the role before it can, and more:
| Role | What it adds |
|---|---|
| Viewer | Sees every page but Billing, settings and the Audit log, and changes nothing. |
| Operator | Runs the node groups: pause and resume, the emergency stop, maintenance on a group or a server, the server count, approving or rejecting proposals, switching between Propose and Live, taking a new release and making an earlier one current, replacing older servers, the deploy lock, a one-off capacity hold, destroying a server or retrying its deletion, refreshing a report, reading a project again. |
| Admin | Shapes them: settings and SSH keys, the deployment method, recurring schedules, the snapshot cleanup, promoting the seed, the steps to Live, connecting projects and replacing their tokens, quarantined servers, the Archive, integrations, the organisation’s profile and the members with their roles. Reads the audit log. |
| Owner | Billing and handing the organisation over. |
API tokens follow the role:
- a viewer’s tokens only read (Read nodes, Read groups, Read metrics);
- an operator’s also Report nodes, Change releases, Lock groups and Replace older servers;
- an admin’s can do everything, Change groups included.
Every request checks the role at that moment, so lowering a member’s role stops their tokens’ writes
at once with 403 forbidden; the tokens themselves are not touched. Every member revokes their own
tokens; the owner or an admin revokes anyone’s.
On another plan every member is the owner or an admin. After moving off Team, viewers and operators keep their roles; an admin can make them admins or remove them, but nobody is made a viewer or an operator.
What happens when someone leaves or is removed?
The owner or an admin removes a member with Remove, never the owner; a member can Leave. Access ends at once, and the member’s API tokens in the organisation are revoked, so a pipeline using one stops. What they did keeps their name. The owner makes someone else the owner before leaving.
How do I delete my account or an organisation?
Write to support@hetscale.com from your account’s address; for an organisation, its owner writes. An organisation can be deleted only once its plan has ended: after you cancel the plan on the Billing page, the deletion waits until the end of the period you paid for. Its data goes with it, its audit log included. Deleting your account deletes the organisations you own alone, under the same rule, and leaves the others as a member leaves; in an organisation you own with other members, use Make owner first. Servers, snapshots and placement groups Hetscale created stay in your Hetzner project with their labels; delete them in the Hetzner Console. Leaving Hetscale lists them, with the steps before the mail. The privacy page says what is kept.
What happens after a downgrade?
Nobody is removed. The Members page warns, and new invitations and joins wait until the members are below the seats.
Which mails do members get?
Every member receives the alert, report and monthly summary mails.