Overview
An Aviate subscription is not limited to the person who bought it. The owner of the subscription creates an organization and invites members: colleagues from sales, finance, support or operations who work in Aviate with their own login. Each member has a role, which decides what they can see and change.
This guide explains how to set up your organization, invite members, change their role and revoke their access.
Key Concepts
| Term | Meaning |
|---|---|
Owner |
The person who holds the Aviate subscription. The owner always has the |
Organization |
The owner’s team. It has a unique name, chosen by the owner. |
Member |
A person the owner invited. A member uses the Aviate features included in the organization’s plan, with their own Aviate login. |
Role |
A Kill Bill role that lists what the member can do, in Kill Bill and in Aviate. New members get |
Members never see or use the owner’s Kill Bill credentials: they connect to Kill Bill with their own Aviate login, and Kill Bill applies their role. This requires a Kill Bill deployment that accepts Aviate tokens (see Accept Aviate Tokens in Kill Bill). On a deployment that doesn’t, Aviate asks the member for their own Kill Bill username and password.
Prerequisites
-
An Aviate subscription. You must be its owner.
-
Access control enabled on each Kill Bill deployment your organization uses, and the roles you plan to give members defined there. See Enabling Access Control. Deployments hosted by Aviate are already set up.
Step 1: Create Your Organization
-
Sign in to Aviate.
-
Open your profile from the account menu, and select the Members tab.
-
Enter a unique Organisation name, for example
acme-corp, and click Create organisation.
You only do this once. The Members tab then lists your members.
|
Note
|
If your organization uses single sign-on, skip this step: the Aviate support team creates your organization and makes you its owner when it sets up SSO. See Aviate Single Sign-On. |
Step 2: Invite a Member
-
On the Members tab, click Invite member.
-
Enter the person’s Email address.
-
Pick a Role. Aviate lists the roles defined on the Kill Bill of your current deployment. If it cannot read them, type the role name. Leave it empty to give
aviate_read. -
Click Send invitation.
The member appears with the status Pending.
|
Note
|
The role must exist on every Kill Bill deployment the member uses. On a deployment where it does not exist, the member can read Kill Bill data but cannot read Aviate data or change anything. |
Step 3: The Member Accepts
Aviate does not send an email: let the person know you invited them. Then they:
-
Sign in to Aviate with the email address you invited, or sign up with it if they don’t have an Aviate login yet.
-
Open their profile from the account menu, and select the Invitations tab.
-
Accept the invitation from your organization.
Their status becomes Active. If they decline, it becomes Declined.
If your organization uses single sign-on, there is nothing to accept: the member’s first sign-in through your identity provider accepts the invitation. See Aviate Single Sign-On.
Change a Member’s Role
On the Members tab, pick a new role in the Role column of a Pending or Active member. The change is saved at once, and applies the next time the member’s session is refreshed.
A role that is not defined on the Kill Bill of your current deployment is shown as (not in this Kill Bill).
Revoke Access
On the Members tab, click the revoke button (×) of the member and confirm. The member immediately loses access to your organization, and their status becomes Revoked.
Member Statuses
| Status | Meaning |
|---|---|
Pending |
Invited, has not accepted yet. You can change the role or revoke the invitation. |
Active |
Accepted the invitation, or joined through single sign-on. |
Declined |
Declined the invitation. |
Revoked |
Access revoked by the owner. |
What Members Can Do
-
Use the Aviate features included in your organization’s plan, within the limits of their role.
-
Add and manage their own Kill Bill deployments in Aviate. Deployments are saved per user, in the browser, and are not shared with the rest of the organization.
-
Call the Aviate and Kill Bill APIs with their own ID token. For members with an Aviate email/password login, see Aviate Authentication for instructions on obtaining a token. That password-based authentication flow does not apply to SSO members.
A request outside the member’s role is refused with 403 Forbidden.
Related
-
Aviate Access Control — roles and permissions
-
Aviate Single Sign-On — let your colleagues sign in with your identity provider
-
Aviate Deployment Management — add Kill Bill deployments to Aviate