Connect your apps
Connect the apps you work in so Glean can use them in answers and, where supported, take actions in them for you. Each connection uses your own account, so Glean never shows you anything you can't already see in the app.
Understand what connecting does
Your admin decides which apps your organization connects to Glean. Connecting one of those apps to your own account signs Glean in as you. After that, Glean can:
- Run tools in the app, such as drafting a reply, updating a record, or pulling live data.
- Show results from apps that require each person to sign in before their content appears, such as Microsoft OneNote or Jira and Confluence on Atlassian Cloud.
- Surface where you're tagged or assigned in the app on your Home page. See Mentions.
Connecting doesn't change your permissions. Glean acts with the access your account already has in the app.
Connect an app
You can connect apps ahead of time from your settings. If you skip this, Glean prompts you with a Connect button the first time you use a tool that needs your account.
Open your connector settings
In Glean, click your profile picture and go to Your settings → Connectors.
Select the app
Sign in and approve access
Sign in to the app with your work account and approve the access request.
The app shows as connected in Your settings → Connectors. Some apps also list their tools with an access level, such as Always allow or Needs approval, which controls whether Glean asks before running each tool.
Why an app you use isn't listed
Your settings → Connectors only shows apps your admin has turned on for your organization. If an app you use is missing, your admin hasn't set up its connector, or hasn't made its tools available to you.
When you ask your admin, include:
- The app's name, and the site or workspace you use if your company has more than one.
- What you want Glean to do with it, such as search its content or update records in it.
Some apps also need a one-time approval from an admin inside the app itself before anyone can connect. For example, a Jira site admin authorizes Glean once for the whole Atlassian site.
Why a connected app still returns nothing
New content takes time to reach Glean. Glean indexes new content within 15 minutes for most apps, such as Jira, Confluence, and Slack. Apps with stricter API limits, such as Zendesk and Salesforce, can take up to an hour. If content still hasn't appeared after that, contact your Glean admin.
If the content is old and never appears, check that your account can open it in the app. Glean only returns what your account can access there.
Why a tool didn't run
When Glean describes how to do something instead of doing it, and no Connect prompt appears, the cause is usually the reasoning mode, not your connection. Tools from connected apps don't load in Fast mode, so there's nothing for Glean to run or ask you to authorize.
On a Customer Key, select Thinking in the chat input and send the request again. See Glean returns instructions instead of running an action.
Troubleshooting
If you have trouble signing in after you connect an app, find what you see in this table and follow the link to the fix.
| What you see | Likely cause | What to do |
|---|---|---|
| Glean asks you to reconnect | Your sign-in expired or was revoked in the app | Click Connect again. See Why a tool keeps asking you to reconnect. |
| Glean uses the wrong account | You signed in to the app with a different account | Disconnect and connect again. See Reset your own authorization. |
| Connect fails or shows no sign-in screen | The app needs admin approval or its setup is incomplete | Contact your admin. See When to contact your admin vs. Glean Support. |
See also
- How Glean accesses information — how Glean finds and cites content from your connected apps