Skip to content

Setup Checklist

In this section, you will find two checklists to help ensure an accurate and streamlined configuration of your company's Glean environment.

Pre-Deployment Checklist

Glean operates on a single-tenant architecture and builds each new customer environment from the ground up.

Please ensure you have communicated the following information to Glean to ensure that your tenant is deployed correctly:

  • Administrator Emails:
    Provide the email address of at least one administrator who will be setting up Glean.
  • Email Domains:
    Provide 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 we are not aware of for security reasons. E.g. company.com for user@company.com

  • Deployment Region:
    Provide the country where you would like your Glean tenant to be hosted.

    Info

    By default, Glean establishes all new tenants in the USA, specifically in the GCP region us-central1, unless otherwise specified.

    Hosting in certain regions may increase your Glean licensing costs to compensate for the higher infrastructure expenses in those regions. For details, please reach out to your Glean account team.

    Error prevention

    Once deployed, your region selection is final.

    A change in hosting region necessitates a complete rebuild of your tenant by Glean.

Info

This checklist is for organizations that are hosting Glean tenant within their own GCP or AWS environments.

General

  • Administrator Emails:
    Provide the email address of at least one administrator who will be setting up Glean.
  • Email Domains:
    Provide 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

  • Deployment Region:
    Provide the country where you would like your Glean tenant to be hosted.

    Info

    By default, Glean establishes all new tenants in the USA, specifically in the GCP region us-central1, unless otherwise specified.

    Hosting in certain regions may increase your Glean licensing costs to compensate for the higher infrastructure expenses in those regions. For details, please reach out to your Glean account team.

    Error prevention

    Once deployed, your region selection is final.

    A change in hosting region necessitates a complete rebuild of your tenant by Glean.

Google Cloud Platform (GCP)

  • The GCP Deployment Guide has been followed:
    • A GCP project name, ID, and number have been communicated to Glean.
    • Billing information has been correctly set for the environment.
    • All required GCP APIs have been enabled for the project.
    • Applicable quota increases have been submitted and approved by GCP for the project and the GCP region & zone selected.
    • A service account owner key for the project has been provided to Glean in JSON format.

Amazon Web Services (AWS)

Info

Glean support for AWS is currently in beta. Contact your Glean account team for more information.

  • The AWS Deployment Guide has been followed:
    • An empty AWS account owned by your organization has been created.
    • Billing information has been correctly set for the environment.

Initial Setup Checklist

To ensure a smooth initial setup process for Glean, follow this checklist to ensure all necessary items, people, and resources are on-hand and ready:

  • SSO Administrator & Information:
    You will need an administrator of your Single Sign-On (SSO) provider on-hand to configure SSO for Glean.
  • People Data CSV:
    If you are using SAML for SSO instead of OIDC, you will need a CSV file containing the directory information for the users who will access Glean. If you are uncertain about this requirement, please contact your Glean account team.
  • Data source Administrators:
    You will need an administrator for each data source or cloud-app you wish to connect to Glean (e.g., M365, Atlassian, Slack, GitHub). These administrators will either authorize the installation of the Glean app within their respective data source or create a scoped API token for Glean's use.