Items to prepare

Every organization has a long list of applications that require connection and integration with Glean.

To speed up your time to value, you should identify 4 to 6 "mission critical" apps to integrate first. For example, SharePoint, Outlook, Google Drive, Jira, Confluence, Zendesk, etc.

These should be the core applications that have the largest user footprints within your organization. At a bare minimum you should ensure you have in scope at least:

• One document repository app (SharePoint, OneDrive, Google Drive, Box, etc)
• One communications app (Teams, Slack, etc)

You can add any apps outside of this core scope later.

tip

Why can't every app be connected upfront?

Before Glean can be used, a full fetch of data from core apps needs to be completed so that your search algorithm can be created. The algorithm cannot be created before this is complete.

If the focus is on connecting every application in the organization upfront, you will significantly delay the point at which our training workflows can be started, and in turn, the point at which users can start using the service.

One of the biggest delays encountered by customers when setting up Glean is the internal approvals needed (both from an application owner and security perspective) to connect each app to Glean.

We recommend initiating the approval process as early as possible to avoid any unnecessary delays. Start by:

• Identifying the key stakeholders within your organization who are responsible for application ownership and security.
• Schedule meetings or consultations with these stakeholders to discuss the integration of Glean and address any concerns they may have.
• Provide them with detailed documentation about Glean's security protocols, compliance certifications, and data handling practices to facilitate a smoother approval process.
  tip

Some of this information may require an NDA. Please contact your Glean account team for more information. :::

• Prepare a clear and concise summary of the benefits and functionalities that Glean will bring to your organization, which can help in gaining their support.

If you are opting for a self-hosted deployment of Glean, it is crucial to prepare your cloud environment in advance by following the preparation guide of the cloud provider you are choosing. To do this, please work with your internal administrator of the cloud provider.

This will involve:

1. Picking one of the supported regions of the cloud provider.

2. Correctly setting billing information for the environment.

3. Enabling all the required services

4. Adjusting the quotas of the cloud provider

5. Providing Glean with details of the environment including:

   • (GCP) The project ID, name, number, and the selected region
   • (AWS) The account ID, name, and the selected region

For detailed documentation on the requirements for creating the environment, please refer to the docs for GCP or AWS.

If not launching to the entire company at once, you should identify the initial group of users who will test Glean, and provide feedback on the system. Consider the following when selecting users to pilot Glean:

• Diverse Representation: Choose users from different departments and roles to ensure diverse feedback and comprehensive testing.
• Tech-Savvy Users: Select users who are comfortable with technology and can quickly adapt to new tools.
• Key Stakeholders: Include key stakeholders who can champion the adoption of Glean within their teams.

Once identified, provide these users with the necessary training and resources to get started with Glean (we can help!). Their feedback will be invaluable in fine-tuning the system before a broader rollout.

• SSO Integration: Ensure that your SSO provider is ready for integration with Glean. Glean supports a variety of SSO providers, including Okta, Azure AD, and Google Workspace. You should have the necessary permissions to configure SSO settings in your IdP. Glean requires SSO integration to be complete before end-users can access Glean.
• People/Directory Data: Ensure that your people data is up-to-date and accurate in your people data source. Glean uses this data to provide personalized search results and recommendations to users. The important fields are First Name, Last Name, Email, Title, Team, Department, Location, and Manager Email. People data is a required item.

tip

In most organizations, people data is already synced to the SSO provider you are using and both the SSO and People data can be configured by the same person.

A well-structured timeline ensures smooth deployment and sets appropriate expectations.

• Project Plan: Develop of a detailed project plan that outlines all the key milestones, tasks, and deadlines associated with the deployment.
• Resource Allocation: Ensure that you have allocated the necessary resources, including personnel, to assist with deployment of Glean.
• Risk Management: Identify potential risks and develop mitigation strategies to address any issues that may arise during the deployment process.
• Communication Plan: Establish a communication plan to keep all stakeholders informed about the progress of the deployment. You should also ensure that mechanisms to collect and aggregate user feedback have been identified.