---
title: First Time Admin
slug: first-time-admin
icon: {"lucideIcon":"ShieldUser"}
docTags: 
createdAt: 2025-11-14T22:57:13.518Z
---

# Overview

This guide is a step-by-step walkthrough of the SHI One onboarding process. Note that the person who performs this onboarding process will have Admin permissions in SHI One. Other users designated as Admins can be added after onboarding is complete.

The onboarding process has three parts:

1. Complete the SHI One Organization Registration
2. Choose how your organization's Users will sign in
3. Set up Security Groups

If your organization's SHI One account has already been set up, jump ahead to [First Time User](docId:_ryKl3RQhVEI_kpjqpilD).

***

# Initial Account Setup Login for Admin

Use Chrome, Edge, or Firefox as your browser. Internet Explorer is not supported.

1. When you receive the SHI One Portal Onboarding email, click the **Start Onboarding Process** button
2. Confirm your email address
3. A verification code is sent to your email, which you then confirm
4. Fill in the **SHI One Organization Registration**
5. Choose how your organization's Users will sign in:
   - Microsoft Office 365/Entra ID SSO (Recommended)
   - Google SSO
   - Okta SSO
   - Register New SHI One User Accounts

:::hint{type="info"}
If your organization would like to use a sign-in option that is not listed above, reach out to your SHI account team to explore available options and review the requirements.
:::

***

## Microsoft Office 365/Entra ID SSO

If you select Microsoft SSO, you will be asked if you are an O365/Entra ID admin:

- If you <u>ARE</u> an O365/Entra ID admin, you can authorize the SSO connection by clicking the **Grant Tenant-Wide Admin Consent to SHI One** button
- If you are <u>NOT</u> an O365/Entra ID admin, send the below URL to your organization's O365/Azure admin (usually someone on your IT team) to authorize the application on your behalf:
  - `https://login.microsoftonline.com/common/adminconsent?client_id=612f0fa7-b4f7-44b9-8684-5e0c36200771`

*Admin consent allows SHI One to read user profiles and enable SSO login. No other tenant data is accessed.*

The O365/Azure admin's email address domain <u>**must**</u> match the organization's email domain in SHI One.

- If the email for the account in SHI One is @bird.com then the O365/Azure admin's email must also be @bird.com
- If the email for the account in SHI One is @bird.com but the O365/Azure admin's email is @bird.onmicrosoft.com, they will not be able to grant permission or sign in to SHI One
  - To add a second email domain to your SHI One account, see [Getting Started](docId\:zVmalv-PTCduJpafma4XF).

***

## Setting Up Google SSO

To grant SSO permissions to SHI One, you have two options:

1. If you are a Google admin, sign in to Google and authorize the SHI One application
2. If you do not have permission to grant authorization yourself, contact your organization's Google admin (usually someone on your IT team) to authorize the application on your behalf

The Google admin's email address <u>**must**</u> match the organization's email in SHI One.

- If the email for the account in SHI One is @bird.com then the admin's email must also be @bird.com
- If the email for the account in SHI One is @bird.com but the Google admin's email is @bird.google.com, they will not be able to grant permission or log into SHI One
  - To add a second email domain to your SHI One account, see [Getting Started](docId\:zVmalv-PTCduJpafma4XF).



***

## Okta SSO

For more information about setting up Okta as the identity provider for SHI One, see the [Okta](docId\:tqhdFxJFujXsTdw0r7plO) integration guide.

***

## SHI One Manual Account Registration

Choosing this option requires <u>all Users</u> to manually register their accounts the first time they sign in.

1. Fill out the **SHI One Organization Registration**.
2. Verify the registration.
3. Click on **Register an Account**.
4. Verify your email.
5. Sign in.

***

# Security Groups

:::hint{type="warning"}
Once these steps are complete, see [Security Groups](docId\:BqVUyIv9EIX4klu0n_Dip) to complete the onboarding process. <u>**Onboarding is not complete until Security Groups are configured.**</u>
:::