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
- Scope. Choose the supported platform URL, folder and Lolly Work groups. Explicitly configure the workflow states that should count as approved.
- Connection. Obtain the tenant API key described below and follow the four-step connection.
- 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.
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
- Your platform URL: your tenant's address, such as
https://acme.intelligencebank.com(theplatformUrloption). It must be onintelligencebank.com; tenants on a custom domain are not supported yet. - An API key for that tenant with read access to what you want to federate. The driver logs in with it through IntelligenceBank's documented handshake and finds the tenant's v3 API address itself, so you never configure that address.
- Which workflow states count as approved in your tenant, for
approvedStates.
Credential shape
A single sealed string: the tenant API key used for the login.
lw providers credential acme-ib # prompts; never argv, never shell historyinstance.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" }
}options.platformUrl(required) is your tenant URL, where the login happens.options.approvedStateslists the workflow states that count as approved.options.folderIdfederates one folder.- IntelligenceBank's own publish, expiry and review dates import as an availability window with no mapping.
approvedStates, every asset federates as approvedWorkflow 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-ibA login <status> error means the platform URL or the API key is wrong.
Notes / limits
- v3 Graph API only. Nothing uses the deprecated v2 resource endpoints. The one v2-named call is the login, which IntelligenceBank defines as the way to sign in to v3.
- Pinned hosts. The discovered v3 address and every download are pinned to the
intelligencebank.comhosts; aplatformUrlelsewhere is refused.
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.