Glean’s 15Five connector allows organizations to integrate data from the 15Five performance management platform into Glean’s search experience. The connector ingests publicly available content from 15Five, including employee recognitions and weekly priorities, and strictly enforces data security and permissions according to the user’s access in 15Five itself. Only data authorized by the connected system and based on 15Five’s provided API is available to users during search.

​
Supported Features and Limitations

The 15Five connector is designed to bring core collaborative content from 15Five to Glean’s unified search. It makes 15Five’s public recognitions and weekly priorities discoverable, while preserving access controls.

​
Supported Objects/Entities

Object/EntityDescriptionNotes
PrioritiesWeekly goals tracked in 15FiveIndexed as user documents; visible to self/manager only
High FivesPublic recognitions among employeesOnly public “High Fives” and comments supported

​
Supported API Endpoints/Features

  • Fetches via 15Five Public API:
    • /api/public/priority
    • /api/public/high-five
    • /api/public/group (for membership/permissions)
  • Indexes metadata to enforce permissions at search-time

​
Limitations

  • Only public High Fives and public comments are indexed (as permitted by 15Five’s API)
  • Private High Fives and private comments are not indexed
  • Only priorities marked as “complete” are surfaced (API limitation)
  • No indexing for 15Five “Objectives,” “1-on-1s,” or “Best-Self Review” at this time
  • Multi-instance setup is supported; each requires unique credentials
  • Known platform bug with group-based visibility has been resolved (see EN-71650)

​
Requirements

To set up the connector, certain technical and credential conditions must be met. This section describes prerequisite systems access and permissions needed for successful connection.

​
Technical Requirements

  • Access to a 15Five instance with admin privileges
  • Glean deployment with internet access to my.15five.com and the appropriate 15Five subdomain (e.g., glean.15five.com)

​
Credential Requirements

  • A 15Five API access token, created by a 15Five admin through the 15Five UI
  • Customer’s 15Five subdomain

​
Permission Requirements

  • The access token must be generated by a user with 15Five admin privileges
  • Permissions must be granted that allow API access to public High Fives and Priorities
  • Admin-level access ensures all needed features/data are accessible and underlying user permissions are respected

​
Preliminary Source/System Setup

  • Ensure the 15Five Public API is enabled (may be on by default)
  • Generate and copy the API access token via the 15Five UI
  • Confirm the correct 15Five subdomain is used (may appear in SAML settings or login page)
  • For multi-instance support, repeat setup with unique tokens/subdomains as needed

​
Configuration and Setup Instructions

You will perform configuration primarily in the Glean Admin console, with prerequisite preparation done in your 15Five environment.

​
Prerequisites

  • 15Five admin privileges to access API settings and generate tokens

​
Generate and upload an access token for 15Five

  1. Glean integrates with 15Five using an API token. If you have not set up any integrations for 15Five yet, please follow their guide for enabling integrations.
  2. Once you have enabled the public api, you can create a new key from this page.
  3. Create a new key from this page, making sure to not select the “High Fives only” option
  4. Enter this new API token from step one into the API token input box in the Glean admin console.

​
Determine your 15Five instance name

  1. Go to this 15Five page, and copy the value from the Subdomain text box into the 15Five Custom Subdomain field.
  2. For example, if your URLs look like https://glean.15five.com/..., enter glean into the box.
  3. Select Save in Glean.