4.4.2. Multisite FAQ

Data Retention: How does it work?

Data retention in Strawberry determines whether project files remain stored on the source system when a project is transferred to another site. When the “Retain Data” option is enabled, project files stay on the source system, even though metadata is removed from the database. This ensures that users no longer see the project in their interface, but the actual files still exist on storage.

• More information on data retention

Storage: What is the role of Lucidlink in a multisite system?

LucidLink acts as the transport layer in Strawberry’s multi-site setup, enabling cloud-based project transfers. It ensures efficient file synchronization between different locations,

How is user creation and deletion handled?

• User creation events are broadcasted across systems but not fully synchronized. This means that when a user is created on one Multisite system, their account will be automatically created on other connected systems. If a central identity provider supporting OpenID Connect (e.g., AD, Azure AD, OKTA, MyID) is used, users can access other sites without further administrative action. For user accounts that do not rely on a central identity provider, user creation on other Multisite systems occurs, but an Administrator must manually assign passwords for these users on the other sites.

How is project and asset metadata handled in Multisite transfers?

Projects originating from another site (foreign projects) cannot exceed their original Metadata/Status scope, meaning that they can currently not be assigned metadata from a site that isn’t their origin.

How are proxies handled in Multisite transfers?

Proxies are copied each time a project is transferred between sites, regardless of data retention settings (i.e., data retention policies do currently not apply to proxies).