This guide is self-contained — every permission and access requirement is listed in the steps below. For why each permission is needed, the full permission model, and propagation latency details, see Permissions & Security - Kontainer.

Prerequisites

Who you need to be

• A Kontainer administrator, or a user with access to Settings → Configuration → API to generate an API token

• A Simpplr Enterprise Search administrator

Network and firewall

• Simpplr Enterprise Search must be able to reach your Kontainer tenant host (e.g., https://acme.kontainer.com) on HTTPS (port 443). No additional IP allowlisting is required unless your Kontainer tenant has custom network restrictions.

Step 1 — Prepare Kontainer

Credentials you will need from Kontainer

• Tenant domain (e.g., acme.kontainer.com)

• API token

1. Identify your Kontainer tenant URL.
   Your Kontainer tenant host is typically a dedicated subdomain (e.g., acme.kontainer.com), not app.kontainer.com. Confirm this with your Kontainer administrator if unsure.

2. Create a dedicated integration user (recommended).
   In Kontainer, go to Access → Users and create a service account for this connector (e.g., enterprise-search-sync@yourcompany.com). Using a dedicated user avoids disruption if an individual's account changes.

   

3. Grant the integration user Download access on DAM folders.
   Assign the integration user to a group — or grant direct folder-level permissions — so they have at minimum Download access on all DAM folders you want to index (see Permissions & Security - Kontainer for why this is needed).

   • Download access on DAM folders — to read DAM file content, metadata, and folder structure for indexing

   • User and group API access (admin-level or equivalent) — required only when document-level security (DLS) is enabled; allows the connector to read user profiles and group memberships for permission sync

   

4. Generate an API token.
   Log in to Kontainer as an administrator, then go to Settings → Configuration → API → New Token. Generate a token for the integration user and copy its value — you will need it in Step 2.

   Token validity: API tokens have a maximum validity of 2 years. Set a reminder to regenerate the token before it expires. An expired token will cause sync failures with an authentication error.

   

Step 2 — Add Kontainer as a source in Simpplr Enterprise Search Admin Panel

1. In Simpplr, go to: Manage Features → Enterprise Search → Add Source.

   

2. Search for, and select Kontainer.
   

3. Enter a Connection Name for this instance.

4. Enter the credentials from Step 1:

   • Domain: your Kontainer tenant domain (e.g., acme.kontainer.com)

   • API Token: paste the token generated in Step 1

   

5. Click Save configuration and confirm.

Note: This creates the connector, but data sync does not begin yet. You can set up filters and ingestion scope in the next step before the first sync runs.

Step 3 — Add filters and ingestion scope

Filters control which content gets indexed. All filters are optional

1. Set DAM folder scope (optional)

   • Include specific folders: index only content within selected DAM folder paths

   • Exclude specific folders: skip content within selected DAM folder paths and their descendants

2. Set DAM Age (optional, exclusion only)

   • Age — limit DAM indexing to files updated after a specified date
     

3. Set Audience configuration (optional) — restrict the connector to a specific Simpplr audience. Only members of the selected audience will be able to find this content in Enterprise Search.

4. Click Save and sync — this saves the configuration and initiates the first full sync.

   Alternatively, click Exit to save and resume setup later. To start the sync manually, go to Enterprise Search → Kontainer → Status and click Sync now.

Step 4 — Verify the sync

1. Monitor progress at: Enterprise Search → Kontainer → Status.

2. The dashboard shows sync status, total items indexed, and any errors.

    

What success looks like:

• Within 15 minutes of starting the sync, the status shows In progress and the item count begins increasing.

• When the initial full sync completes, the status shows Success and Kontainer results appear in Enterprise Search for users with access.

• Initial full sync duration depends on content volume — tenants with large DAM libraries may take several hours.

If the sync stays in Pending, fails, or completes with far fewer items than expected, see Troubleshooting - Enterprise Search Connectors.