Teams and roles

In Aloft, everything you create — monitors, notification channels, status pages, maintenance windows, API keys, and post-mortems — belongs to an organisation, not to you personally. Organisations are how you share that work with a team and control who can change what.

Personal and shared organisations

Everyone automatically gets a personal organisation the first time they sign in. You’re the owner, and it works as your own private workspace.

When you want to collaborate, create additional organisations — one per team, customer, or project. You can belong to as many as you like, with a different role in each.

Switching organisations

You’re always operating “inside” exactly one organisation at a time — the current organisation. Everything you see and create belongs to it.

Once you belong to more than one organisation, an organisation switcher appears in the top bar (it stays hidden while you only have your personal org). Open it, then pick an organisation from the Switch organisation list to make it current. A checkmark marks the one you’re in now.

Note

Because resources are scoped to the current organisation, switching changes the monitors, channels, status pages, and API keys you see. If something seems to be “missing”, confirm you’re in the right organisation first.

Creating an organisation

1. Open the organisation switcher and choose Manage organisations (or go to the Organisations page directly).
2. Under Create an organisation, enter a name and submit.
3. You become the owner of the new organisation and are switched into it.

Inviting members

Invitations are sent by email and let someone join your organisation with a specific role.

1. From Organisations, choose Members on the organisation you want to grow.
2. In Invite a teammate, enter the person’s email address and pick a role.
3. Send the invite. Aloft emails them a link that expires in 7 days.

Notes:

• Only owners and admins can invite.
• You can’t invite someone at a role higher than your own.
• The invitee must accept using the same email address the invite was sent to.
• Pending invites appear under Open invitations, where you can Cancel one before it’s accepted.

Accepting an invitation

The invited person clicks the link in their email. After signing in (or signing up) with the matching email address, they’re added to the organisation and switched into it automatically. If the link has expired, was already used, or the email doesn’t match, they’ll see an explanation instead.

The four roles

Every membership has one of four roles. Lower in this list means fewer permissions:

• Owner — full control, including deleting the organisation.
• Admin — manages people and resources, but can’t delete the organisation.
• Member — creates and edits resources, but can’t manage people.
• Viewer — read-only access.

What each role can do

Action	Viewer	Member	Admin	Owner
View monitors, channels, status pages, etc.	✓	✓	✓	✓
Create / edit monitors, channels, status pages, maintenance		✓	✓	✓
Manage API keys			✓	✓
Invite / remove members, change roles (up to your own rank)			✓	✓
Delete the organisation				✓

Changing roles and removing members

From an organisation’s Members page (owners and admins only):

• Change a role — use the role selector next to a member. You can’t promote someone above your own role.
• Remove a member — choose the remove (trash) action next to them. Anyone can remove themselves from an organisation; removing others requires admin or owner.

The “at least one owner” rule

An organisation must always have at least one owner. Aloft blocks any action that would leave it without one — so you can’t demote the last owner to a lower role, and you can’t remove the last owner. To hand off ownership, promote another member to owner first, then change or remove the original owner.

What belongs to an organisation

Keep in mind that the following are scoped to whichever organisation you’re currently in:

• Monitors and their notification channels
• Status pages (see Status pages) and their incident posts and subscribers
• Maintenance windows
• Incident post-mortems
• API keys — a key is bound to the organisation it was created in and grants access to that organisation’s resources, regardless of who created it.

So before you create something, make sure you’re in the organisation where it belongs. To move work to a different team, switch organisations first, then create it there.