Your digital asset management system can remain the source of record while Lolly helps people make new content from its approved assets. Lolly Work connects a selected part of the library to Lolly tools, applies organisation access rules and provides shared review and delivery services. Migration is optional.
This arrangement suits teams that already have a curated library and administrators who own its approval practices. They can introduce new production tools while keeping those responsibilities visible.
Which system controls each decision?
| Decision | Responsibility |
|---|---|
| Source record, current files and upstream approval | The connected DAM, within the selected connector's supported API |
| Which part of that library reaches Lolly | Work's provider configuration, exposure rules and mapped availability |
| What a person can change in a design | The Lolly tool and design system, plus Work input policies for governed operations |
| Who can review a submission or delivery | Work's configured approval chain and grants |
| Whether a particular use is licensed | The rights holder's permission and the organisation's rights process; source approval alone does not answer this |
| What leaves through an organisation destination | The explicit delivery action, its permission checks and any configured final-byte review |
The flow is: source DAM → governed catalog → Lolly tool → finished output → chosen destination. A source connection normally reads references and files. Outbound delivery has its own credentials and permissions.
Start with one workflow
- Choose one recurring output, such as an event card, and identify its source assets and administrators.
- Use the relevant provider guide to connect a narrow library slice. Preview the listing before enabling access.
- Map approval, group exposure and availability where the connector supports them. Compare an original's checksum with a direct download from the source.
- Open the assets in a tool, make a permitted variant and review its finished output. Test with a member who should have access and one who should not.
- Change or withdraw a source upstream, refresh the connection and observe what happens to listings, previews and new file reads.
Create on-brand content from approved DAM assets turns those checks into a campaign workflow. SUSE's Brandfolder account explains the adoption and change-management experience behind this approach.
Does Work preserve each person's DAM permissions?
The current providers generally use an administrator-configured shared credential. They do not sign every member into the source under that member's upstream identity. Work exposure rules must therefore restrict the credential's wider view to the intended audience. A successful connection is not evidence that the access configuration is correct.
What happens when an asset expires?
Supported upstream availability windows combine with local lifecycle rules, with the more restrictive constraint taking effect. Approval filtering depends on the provider's actual signal and mapping. Some sources have no native approval or expiry field.
Listings can be cached, and upstream changes depend on refresh and file-access behaviour. Work cannot erase a copy someone already downloaded. Agree the acceptable refresh delay and test withdrawal for the workflow you intend to use. Catalog and content describes these boundaries.
Does an approved source make an approved export?
No. Source approval, permission for the proposed use, creative review and approval of finished bytes are separate decisions. Work supports review of exact owned source files and optional approval of staged organisation deliveries. Ordinary exports are not generally bound to reviewed final bytes. Approvals explains the supported paths.
Can finished files go back to the DAM?
Only through a supported, explicitly configured write path. Brandfolder and Cloudinary have organisation delivery adapters; Optimizely CMP has a separate opt-in publish path. Source credentials never automatically grant write authority. Qualify the destination, readback and retry behaviour on your own tenant. See Organisation delivery destinations.
What if we later decide to move?
Keep the working connection while you plan the transition. Supported materialization copies files into organisation storage; cutover can move supported identities while retaining aliases for old addresses. That does not promise a complete transfer of upstream history, rights records or workflows. Plan a DAM transition covers the people and evidence; Leave a DAM covers the commands.