The Seismic connector enables you to search published information in Seismic content profiles directly from Glean. By integrating Seismic with Glean, you can ensure that users only see content they are authorized to access, with permissions enforced down to the record level at query time. This connector is designed to help organizations surface relevant Seismic files while maintaining strict data privacy and access controls.

​
Supported Features and Limitations

The Seismic connector is focused on indexing and searching published content profiles within Seismic. It leverages Seismic’s Reporting API and enforces user-level permissions to ensure secure and relevant search results.

​
Supported Objects/Entities

Object TypeDescription
Content ProfilesPublished information in Seismic content profiles
Library DocumentsDocuments within content profiles (library only)
  • Only published content in content profiles is indexed.
  • Workspace files and unpublished content are not supported.

​
Supported API Endpoints/Features

  • Reporting API: Used to fetch published content profile data.
  • OAuth2 authentication: Ensures secure access and permission enforcement.
  • Custom properties: Can be used to grant document access to specific groups in Glean.

​
Limitations

  • Only published content profiles are indexed, workspace files and unpublished content are excluded.
  • Embedded documents like Google Slides reformatted as PowerPoints are surfaced as links, but their content is not crawled.
  • Seismic’s API does not expose content profile membership, so all published content profile links are made available to all Seismic users in Glean. If a user does not have access to a document in Seismic, they will not be able to view its contents even if it appears in Glean search results.
  • The Reporting API is not included in all Seismic licenses.
  • No support for webhooks, all updates are detected through scheduled crawls.
  • No support for workspace files or unpublished content.

​
Crawling Strategy

Crawl typeFull CrawlIncremental CrawlPeople DataActivityUpdate RateWebhookNotes
Content ProfileYesYesNoYesScheduledNoOnly published content profiles. No webhooks and activity through API
Library DocsYesYesNoNoScheduledNoOnly library not workspace docs and incremental supported
You can configure greenlist (include) or redlist (exclude) folders at the library level to control which folders are crawled.

​
Results Display

Search results from Seismic appear in Glean with document titles, metadata, and links to the original Seismic content. Embedded documents are shown as links, but their content is not indexed.

​
Requirements

To use the Seismic connector, you must meet certain technical, credential, and permission requirements. These ensure secure integration and proper enforcement of access controls.

​
Technical Requirements

  • Access to Seismic with the Reporting API enabled (may require a specific Seismic license).
  • Glean instance with connector integration capabilities.
  • All data is stored in your cloud account; no data leaves your environment.

​
Credential Requirements

  • OAuth2 credentials for a Seismic app.
  • You must register a Seismic app and obtain client ID and secret.
  • The connector requires an access token with the correct scopes (see below).

​
Permission Requirements

  • The Seismic app must be granted the following OAuth scopes:
    • seismic.user.view
    • seismic.user.manage
    Do not use seismic.self.view or seismic.self.manage as these are insufficient for connector operation.
  • The authenticated user must have access to the content profiles you wish to index.
  • The Reporting API must be enabled for your Seismic account.

​
Preliminary Source/System Setup

  • Register a new OAuth2 app in Seismic.
  • Assign the required scopes to the app.
  • Ensure the Reporting API is enabled in your Seismic license.
  • (Optional) Configure custom properties in Seismic to grant document access to specific groups in Glean.

​
Configuration and Setup Instructions

Follow these steps to configure and set up the Seismic connector in Glean. Most setup occurs in the Seismic admin console and the Glean admin interface.

​
Prerequisites

  • Seismic admin access to register and configure OAuth2 apps.
  • Glean admin access to add and configure connectors.
  • Seismic license with Reporting API access.

​
Authentication and Credentials

  • In Seismic, register a new OAuth2 app.
  • Assign the required scopes: seismic.user.view and seismic.user.manage.
  • Obtain the client ID and client secret for the app.
  • In Glean, enter the client ID and secret when adding the Seismic connector.
  • Complete the OAuth2 flow to authorize Glean to access your Seismic data.

​
Step-by-Step Setup

​
Registering a new Seismic app for crawl

To get the client ID and secret from your Seismic tenant for the Glean set up, run the following steps:
  1. Create and register a new app at https://apps.seismic.com/ in the Seismic tenant. Name this app indicating that it is used for Glean integration. Seismic UI screenshot
  2. Setup the Authorization Code Flow
    1. Select OAuth2 - Authorization Code Flow in the Authentication tab. Seismic UI screenshot
    2. On the OAuth2 Information page, add the redirect URL as the tenant URL:
      1. For example, https://yourtenant.seismic.com/.
      2. Client ID is generated automatically.
      3. Generate the client secret. The clieny secret is hidden initially, but you can show and copy the secret. it. Seismic UI screenshot
    3. In the scopes section, select the following scopes:
      • seismic.user.view
      • seismic.user.manage
      • seismic.configuration.view
      • seismic.configuration.manage
      • seismic.reporting
      • seismic.delivery
      • seismic.library.view
      • seismic.library.manage
      • seismic.workspace.view
      • seismic.workspace.manage. Seismic UI screenshot
  3. With the information that you have gathered from the above steps:
    1. Enter the tenant name into the Tenant Name input box. Ensure to not include seismic.com. For example, id the tenant name is https://sciodemo.seismic.com, enter only sciodemo.
    2. Enter the client ID into the Client ID input box.
    3. Enter the client secret into the Client Secret input box.

​
Getting refresh and access token for the app

To get an access and a refresh token for the Glean set up, perform the following steps:
  1. Go the Seismic documentation for instructions and executions of POST requests.
  2. Run the URL given on Get the user’s authorization to get an access code. Note that scopes must be separated by a space in the URL.
  3. Exchange the authorization code for an access token
    1. Go to the Exchange the Authorization Code for an Access Token page.
    2. Enter the required information and click Try it.
    3. The response will have the access token and refresh token. Seismic UI screenshot
    4. Enter the access token into the Access Token input box.
    5. Enter the refresh token into the Refresh Token input box.
  4. Click Save in Glean.

​
Crawl Configuration Options

  • Greenlist: Specify folder IDs in the Seismic library to include in crawls.
  • Redlist: Specify folder IDs to exclude from crawls.
  • Supported file types: Configure which file extensions like pdf, xlsx, pptx and so on must have their content indexed.
  • Custom properties: Use Seismic custom properties to grant access to specific groups in Glean.

​
Permissions & Security

Data and Metadata Ingested:
  • Published content profile documents, metadata (title, author, last modified), and links to embedded documents.
Permission Propagation Logic:
  • Glean enforces Seismic permissions at query time. If Seismic’s API does not expose content profile membership, all published content profile links are made available to all Seismic users in Glean. However, users cannot view content in Seismic if they do not have access.
Security & Compliance Notes:
  • OAuth2-based authentication.
  • All data remains in your cloud environment.
  • No webhooks. All updates are detected through scheduled crawls.
Known Security Restrictions:
  • No support for multi-instance scenarios.
  • All published content profile links are visible to all Seismic users in Glean due to API limitations.
Data Privacy Implications:
  • The connector does not expose unpublished or workspace content.
  • Users cannot access content in Seismic for which they do not have permission, even if it appears in Glean search.
If you have any issues or concerns, reah out to the Glean support team.