1

Phase 1 Apps Identified

You have identified 4-6 “mission critical” apps that will be connected to Glean first. These should be the core applications that have the largest user footprints within your organization. E.g. OneDrive, SharePoint, Google Drive, Slack, Teams, Jira, Confluence.

2

Security & App Owner Approvals

All necessary approvals to connect the above apps to Glean have been obtained from relevant internal teams and/or stakeholders. By proactively managing these approvals, you can significantly reduce the time required to get Glean up and running in your organization.

3

(Self Hosted) Cloud Environment Prepared

If you are deploying Glean to your cloud environment, you have prepared the environment for the build of your Glean environment. Make sure your administrator has followed the creation guide for the cloud provider you are using.

4

Administrator Emails Provided

You have provided Glean with the email addresses of the administrators who will be responsible for managing the Glean environment.

5

Email Authentication Domains Provided

You have provided Glean with a list of all email domains that your users will use to sign in.

Glean does not allow users to sign in from domains that it is not aware of for security reasons. E.g. company.com for user@company.com

6

Deployment Region Selected

You have provided Glean with the country or region where you would like to deploy your Glean environment.

By default, Glean establishes all new tenants in the USA.

Hosting in certain regions may increase your Glean licensing costs (or infrastructure costs if you are self-hosting Glean) to compensate for the higher infrastructure expenses in those regions.

For details, please reach out to your Glean account team.