Content, Sync & Limitations - Kontainer

Content types

DAM files

DAM files are documents and media assets stored in Kontainer's Digital Asset Management (DAM) system. The connector indexes all files the API token user can access. Text content is extracted from supported document formats (e.g., PDF, DOCX, XLSX). Images, video, and other media types are indexed by metadata only.

Fields synced

• Title — Name of the file. Indexed for full-text search; displayed as the result title.

• Body / Content — Text extracted from the file for supported document types (e.g., PDF, Word, Excel). Indexed for full-text search. For images and video, the description field is used instead.

• URL — Direct link to the file in Kontainer (viewer deep-link). Used to generate the result link; not searchable.

• Last modified — Timestamp of the last update. Used for incremental sync; displayed in result metadata.

• Created — Creation timestamp. Displayed in result metadata.

• Author — Email of the user who created the file. Displayed in result metadata.

• Description — File description field. Indexed for full-text search; used as body text for non-extractable file types.

• File extension — Extension of the file (e.g., pdf, png, docx). Used for file type filtering.

• File size — Size of the file in bytes. Used for filtering.

• Folder name — Name of the parent DAM folder. Indexed for full-text search; aids navigation in search results.

• Folder path — Full path of the parent folder. Used for folder-based filtering.

• Folder URL — Direct link to the parent folder in Kontainer. Displayed for context.

• Tags — Keywords and tags assigned to the file in Kontainer. Indexed for full-text search and filtering.

• Custom fields — Dynamic DAM metadata fields configured for the Kontainer tenant (e.g., Collection, Media Type, Status, Usage Rights, Expiry Date). Indexed for full-text search and filtering. Available fields depend on your Kontainer DAM configuration.

Applicable filters

Sync frequency

Incremental sync

After the initial full sync, the connector runs incremental syncs every hour. Each incremental sync pulls DAM changes since the last sync by reading Kontainer operation logs. It captures:

• New DAM files uploaded

• Modified DAM files (renamed, moved, or updated)

• Deleted or trashed DAM files

• DAM file permission changes — only when the file itself is also modified. Permission-only changes (no file modification) are not detected incrementally; see the note below.

Full sync

A full sync re-indexes all content from Kontainer. It runs automatically on first setup, then every day, and can be triggered manually from the connector Status page. Full syncs on large tenants may take several hours. Incremental syncs resume automatically once the full sync completes.

The daily full sync also serves as the safety net for:

• DAM permission-only changes (where folder permissions changed but no file was modified)

User sync

User sync pulls the latest user identities and group memberships from Kontainer and updates the search index. It runs every hour on a separate schedule.

If a user's DAM access is revoked in Kontainer, the change is reflected in Simpplr search results after the next sync completes.

Known limitations

• PIM not supported. PIM products, categories, resources and channels are out of the scope for this connector.

• DAM permission-only changes delayed. If DAM folder permissions change without a corresponding file modification, the change is not detected until the next full sync (daily). This is because Kontainer does not expose an API timestamp for folder-level permission changes alone. To apply such changes sooner, trigger a manual full sync.

• Indexing limited to token user's access. The connector only indexes DAM files the API token user can access in Kontainer. Content outside the token user's permission scope is not indexed.

• Images, video, and media files: text content is not extracted — these files are findable by title, description, tags, and custom fields only.

• Text within images and scanned PDFs: not extracted or searchable.

• API token expiry: Tokens have a maximum validity of 2 years. An expired token causes sync failures. Regenerate the token in Kontainer before expiry and update it in the connector configuration.