Lolly Beta
Launch App

ManageShared assets and provider connections

IntelligenceBank integration with Lolly (kind: intelligencebank)

Note: Lolly Work

This guide covers the optional organisation service. Configuration, console and API paths refer to your Lolly Work instance. The packaged console keeps its release-matched copy of this guide.

Connect an IntelligenceBank DAM and its assets appear in the Lolly Work catalog, with its own expiry and review dates and workflow states carried across. No custom-field mapping is needed. IntelligenceBank stays the source: Lolly Work reads through the current v3 Graph API and never writes back.

Onboarding

  1. Scope. Choose the supported platform URL, folder and Lolly Work groups. Explicitly configure the workflow states that should count as approved.
  2. Connection. Obtain the tenant API key described below and follow the four-step connection.
  3. Tenant check. Run the IntelligenceBank tenant check. Verify the login response, download bytes, publish, expiry and review dates, then test member access and a real production task before broadening the source.
Note: Not yet confirmed live

The driver is not yet confirmed against a live tenant. The login response, field names and download link come from IntelligenceBank's documentation. Check a source on your own tenant lists what to look at. Contributors changing the driver follow its maintainer runbook in the Lolly Work repository.

What you need from IntelligenceBank

Credential shape

A single sealed string: the tenant API key used for the login.

lw providers credential acme-ib     # prompts; never argv, never shell history

instance.json / lw providers add

{
  "id": "acme-ib",
  "kind": "intelligencebank",
  "label": "Acme IntelligenceBank",
  "options": { "platformUrl": "https://acme.intelligencebank.com", "approvedStates": ["Approved", "Published"] },
  "exposure": { "groups": ["brand"], "requireApproved": true, "tier": "reference" }
}
Warning: Without approvedStates, every asset federates as approved

Workflow states differ per tenant, so list the ones that count as approved in yours.

Verify

lw providers preview --kind intelligencebank --options '{"platformUrl":"https://acme.intelligencebank.com"}'
lw providers health acme-ib

A login <status> error means the platform URL or the API key is wrong.

Notes / limits

Off-boarding

IntelligenceBank supports the exit sequence after its tenant check. Qualify publish_date, expiry_date, review_date and the configured approved workflow states; those mappings do not recreate the vendor's review history or complete rights records.

Prepare the destination with the self-hosting strategy with S3 storage, then use Leave a DAM for materialize, drift and cutover. Compare originals, inspect mapped governance on the copies and separately retain required history and unmapped metadata before retiring the tenant.

Compare offboarding destinations, starting with open-source services you can run. Each route remains subject to this source's limits.