/ /

Box connector for Simpplr Enterprise Search

Updated 29 days ago

Introduction

The Box connector allows Simpplr Enterprise Search to index Box Storage content, making it easily discoverable and searchable directly within Simpplr.

With this connector, you can (use cases):

  • Bring Box content into Simpplr Enterprise Search so users can find files alongside intranet content in one place.

  • Respect Box permissions so users only see files they already have access to in Box.

  • Use advanced features like autocomplete, hybrid ranking, and Smart Answers on top of Box content.

Indexed content from Simpplr Enterprise Search is available in:

  • Main search listing

  • Smart answers

Capabilities at a glance

Content types

Folders, Files

Metadata

Title, URL, Owner, Created time and last modified time, Parent URL, File type, extension and size, Mime Type, Permissions (users and groups level access)

Permissions

User and Group based permissions

Indexing

Initial full crawl when the connector is created, followed by a weekly full crawl. Incremental updates run every 4 hours, and ACL (permission) sync runs every hour.

Multiple instances support

Multiple box connections can be configured in the Simpplr environment.

Ingestion Filters

  • Files created/modified within the last 2 years will be ingested by default. Older files are ignored.

  • Basic Filtering : Admins can exclude files from indexing based on:

  • File extension (e.g., .zip, .exe)

  • File size

  • Document age

  • Audience filters - Admins can include/exclude documents from indexing based on the Audiences.

Search features


  • Keyword search

  • Hybrid / semantic ranking

  • Autocomplete suggestions

  • Filters for source, file type, owner, created date

  • Box content can be used in Smart Answers

Objects and content supported

  1. Objects - List the object types that are indexed, for example:

  • Files

  • Folder

  1. Metadata - For each indexed item, Box captures:

  • Title

  • URL / link

  • Owner

  • Created time and last modified time

  • Parent URL

  • File type, extension and size

  • Mime Type

  • Permissions (users and groups level access)

  1. Permissions model - Permissions are read from Box and enforced in Simpplr Enterprise Search. Include: 

    1. How user and group permissions are synchronized

  • Box user and group memberships are fetched and stored in the ACL index.

  • When a user is added to or removed from a Box group, the ACL index is updated the next time the ACL sync runs (by default, every hour).

How public or link-shared content is handled

Content that is only available via anonymous or public shared links is not indexed in the current version of this connector.

What happens when access is removed for a specific document?

  • When a user loses access to a file or folder in Box, the updated permissions are applied during the next ACL sync.

  • The file will no longer appear in that user’s Simpplr search results after the ACL sync completes.

Versions and editions supported

  • Supported Box account editions: Enterprise account.

  • Not supported: Free account

Prerequisites

Before you begin, ensure the following:

  1. Source system permissions

  • You need access to the Box Developer Console to create and configure your application.

  1. Application / service account

  • Ability to register a new Server Authentication (Client Credentials Grant) app in the Box dev console with custom App 

  • Ability to Authorize the application from the Admin console.

Box documentation:

Authentication and security

How does Simpplr Enterprise Search connect to Box?

  • Auth type: Server Authentication (Client credentials)

  • Scopes or permissions required (examples):

    • Write all files and folders stored in Box" in Application Scopes

    • "Make API calls using the as-user header" in Advanced Features

Data security

  1. Data storage and residency: Indexed content and ACLs from Box are stored within your Simpplr Enterprise Search environment, in the same region as your Simpplr tenant.

  2. Encryption in transit: Server-side encryption with Amazon S3 managed keys (SSE-S3), TLS encryption in Kafka.

  3. Encryption at rest: SSL (TLS 1.2 or higher), Auth: OAuth 2.0 Bearer tokens (client-credential).

  4. Permission enforcement: Box access controls (users and groups) are stored in the ACL index and applied at query time. Search results are always filtered by the signed-in user’s identity and Box group memberships.

Setup and configuration

Step 1 - Prepare your Box source

1. Go to Box dev console, click “Create Platform App” and then Click on New App + 

Box n8.png

2. Select “Server Authentication (Client Credentials Grant)”, Click “Create App”.
Box n7.png

Box n6.png

3. Select App + Enterprise access when you create the app 
Box n5.png

4 .On the “Configuration” screen, to the right you will find App details sections Under it , Copy the Client ID and save it
5. Click “Fetch Secret” and copy the Client Secret
Box n4.jpg

6. Note the Enterprise ID under the “General Settings” tab;
Box n3.jpg

7. Check following permissions:
      A.  "Write all files and folders stored in Box" in Content Actions
      B. "Make API calls using the as-user header" in Additional Configuration

box n2.png
7.  Click “Save Changes” 

8 . Authorize your application from the admin console. Go to the "Authorization" tab, click “Review and Submit”
Box n.png

9. Your Box admin will receive an email about the request. Click the email to open the approval page, then click “Authorize” to authorize the app.

Box n9.png

Box n10.png
10. Once authorized, the status in the Authorization tab will change to “Authorized”:

Box n11.png

Step 2 - Create the connector in Simpplr

  1. From your Simpplr home dashboard, go to: Manage features > Enterprise search > Add source.

  2. Search for and select Box.

  3. Enter basic information:

    • Name: (Connector Name for this instance)

  4. Provide authentication details (Copied from the app Server Application):

  5. Click Save, then Confirm

Step 3 - Define sync scope

  • Configure inclusion rules:

    • Not configurable in the current version

  • Configure exclusion rules:

    • File extension (e.g., .zip, .exe)

    • File size above a specified threshold

    • Document age (e.g., older than X days)

  • Configure Audience based filtering.

    • Include audiences

    • Exclude audiences

Step 4 - Configure sync schedule

  • Default schedule: Full crawl at first setup and once in a week, incremental sync every 4 hours, ACL runs every hour

  • Configuration options:

    • No option to configure the sync schedule, however sync can be paused and resumed manually

Step 5  : Box imposes a monthly limit on API calls based on the user's license. To ensure optimal performance, it is recommended to confirm that the number of files and folders being synced is within this limit. If you anticipate exceeding the limit, please contact the Simpplr team with specific folder IDs and the owner's email address for assistance.

Step 6  - Monitor the sync

  1. Monitor the initial full sync status (starts automatically) in the connector dashboard.

Crawling and sync behavior

How the connector works over time:

  1.  Initial full crawl

  • All the content present in the storage account is indexed during the first run

  • How long it may take: Depends on the size of the content

  1. Incremental updates

  • Mechanism: Based on Timestamp of previous sync

  • What changes trigger reindexing:

    • New items created

    • Existing items updated

    • Permissions changed

    • Items moved or renamed

    • Items deleted or archived

  1. Deletion and permission changes

  • Deleted items are removed from index at next sync

  • Permission changes are updated at the next sync cycle

  1. Expected latency

  • With the default schedule (incremental sync every 4 hours and ACL sync every hour), changes made to Box content are generally reflected in Simpplr search results within 4 hours of the update, and the permission lag in the system can be up-to 4hours. (as the incremental Sync every 4 hours). On top of that, there can be certain cases, where the permission sync can take up-to 7days (When the full sync is run), subject to content volume and system load.

Field mapping and search experience

Default field mapping

Source field Box Storage > Index field Simpplr

Title

Name 

url

url

owner/created by

created_by.login

file type

file_type

Last modified

_timestamp

Created data

created_at

size

size

permissions /access control 

_allow_access_control

Search experience - how content from this connector appears in search:

Result layout: (Icon, Connector name, title (name) as link, body(excerpt), owner, Created Date, File Type icon, file type)

  • Available filters and facets:

    • Sources = Box

    • File type

    • Owner

    • Created Date

  • Participation in advanced features:

    • Smart Answers / Q&A: Yes

    • Autocomplete: Yes

    • Recommendations / “Suggested for you”: N/A

    • Trending / popular results: N/A

    • Semantic / hybrid ranking: Yes

Known limitations

Maximum file size indexed

Files bigger than 10 MB won’t be extracted.

Unsupported file types

Compressed files are not supported, e.g., an archive file containing a set of PDFs

(The file content is not searchable, however, the users can still search via file title.)

Rate limits

N/A

Preview limitations

No preview available for excel, or media files.

Permission edge case

Permission changes are not synced unless ACL sync is run.

Other known limitations

The text from the PDF is extracted. However,  If text is within an image, it is not extracted.

Monitoring and troubleshooting

  1. Connector health and monitoring - Describe where admins can see status information:

  • Enterprise Search -> Connector name

  • Available metrics:

    • Last sync status (Success / Warning / Failed)

    • Last sync time

    • Next scheduled sync

    • Sync Type

    • Total items indexed count

  1. Common issues and resolutions - Example pattern:

  1. Common issues and resolutions. Example pattern:

    1. Issue: Authentication failed, Failed to generate the access token (invalid credentials or missing scopes)
      Possible causes:

      1. Incorrect client ID or secret

      2. App not granted the required permissions

      3. App not authorized by the Admin

    2. Resolution:

      1. Verify and re-enter credentials

      2. Confirm required scopes are granted

      3. Confirm if the App is authorized

  2. When to contact support. 

    1. Authentication error persists even after trying the above-mentioned resolutions

    2. Sync is stuck in the Pending state,

    3. Sync is in progress but no documents are getting ingested.

    4. Sync failure with cancelled error (when not cancelled manually)

    5. Incomplete or Partial sync.

  3. When contacting Support, include:

  • Connector name and instance ID (if available)

  • Organization URL

  • Approximate time and date of the issue

  • Error messages or screenshots

  • Steps you already tried

Frequently asked questions (FAQ)

QCan I connect multiple Box tenants or domains?
A. Multiple box connections can be configured in the Simpplr environment.

Q2. How often does Box sync data?
A. The connector runs a full crawl on first setup. Incremental sync runs every hour.

Q3. Are comments, revisions, or version history indexed?
A. Comments and individual versions are not indexed as separate items. The connector indexes the latest file metadata, including the last updated time and updated-by user.

Q4. Does the connector index content from external guests or shared links?
A. No.

Q5. What happens when a user loses access to an item in Box Storage ?
A. The updated access permissions will be indexed during the next sync.

Note: Files and permissions are synced every hour. However, the actual update time may vary depending on the volume of data created within that period. Under normal conditions, changes are reflected within 1–2 hours, provided there has not been a significant spike in data uploads.

Q6. Can I exclude certain sites/teams/folders from being indexed?
A. Documents can only be excluded based on file extension, size, and age. Additionally, documents can be included or excluded based on audiences.

Q7. How are deletions handled?
A. Objects deleted from the source are permanently deleted from the index.

Q8. Are image files searchable?

Was this article helpful?
Subscribe to receive updates on this article