# Adding Users to Airkit

### Overview

Once an [Org](airkit-organizations) has been created, users with [admin permissions](managing-user-roles) can invite new users to join. Having an account associated with an Org is required to access any part of that Org, including the [Console](../console/console) and associated [Portals](../building-apps/portals/portal-capabilities). To grant someone the ability to view or work with any part of your Org, you will need to invite them and assign them a [role](managing-user-roles) within it.

Invites are managed in the [Console](../console/console), under Settings -> Invites. Again, note that **only an admin can invite new users to join an Org**. If you cannot access this part of the Console, it is likely because you are not occupying a [user role](managing-user-roles) that grants you permission to do so:

![Screen\_Shot\_2021-10-06\_at\_4.06.20\_PM.png](https://1191388742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhOn9CLWoV9VfJeM5EDAa%2Fuploads%2Fgit-blob-c9f4bb5ec1af4db4e17a86a28fb2a19b1e51d3f4%2Fadding-users-to-airkit-v1715-0.png?alt=media)

To invite a new user to join your Org, click on the _Create Ne&#x77;_&#x62;utton, fill out the Invite Fields that appear in the Inspector, and then click on the _Create_ button that appears in the bottom left:

![](https://1191388742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhOn9CLWoV9VfJeM5EDAa%2Fuploads%2Fgit-blob-01fb9b612c234f682459bf3c96d9a661ad020cf9%2Fadding-users-to-airkit-v1715-1?alt=media).gif)

### Invite Fields

* **Email** _(required)_ - The email address where the invite will be sent
* **SSO with Google Only** _(checkbox)_- If selected, the user’s Google OAuth credentials (if applicable) can be used to log in
* **Username** _(optional)_- The username that will be given to the invitee If no username is designated here, the user will be allowed to set their own. _Note: usernames are case-sensitive._
* **First Name** _(optional)_- The invitee's first name. If no value is given, the user will be allow to set it themselves.
* **Last Name** _(optional)_- The invitee's last name. If no value is given, the user will be allow to set it themselves.
* **Starting URL** _(dropdown menu, default: Studio)_ - Designates what part of the Org the invitee will be taken to upon first logging in. Options are [Studio](../studio/studio), [Console](../console/console), and [Portal](../building-apps/portals/portal-capabilities).
* **Roles** _(dropdown menu, selection required)_- The [role](managing-user-roles) granted to the invited user. The role a user is assigned defines the permissions and limitations they will have when working inside the Org.
* **User Variables** _(optional)_- Defines what (if any) User Variables (and their associated values) will be associated with the invitee's account. User Variables serve as an additional means of security, as they limit access to [Portal Pages](../building-apps/portals/portal-capabilities) to only users associated with precisely-matching pairs of User Variables and values. For more on how to implement this added layer of security, check out [documentation on the Portal Builder](../studio/builder-bar/portal-builder). _Note: User Variables and their associated values are case-sensitive._

Once an invite is accepted, users with [admin permissions](managing-user-roles) can change the value of these fields, which are managed in the [Console](../console/console), under Settings -> Users.
