Federated projects

Find a shared project

Projects shared with you are kept separate from local projects. They appear in a section named after the server that hosts them. Each source server has its own section.

A federated project is available from your list, but its files are not copied to your server. If it is temporarily offline, it remains listed under its server section and becomes available again when the server reconnects.

Share a project

An administrator opens the project menu, selects Share (federation)…, then chooses the server, people, permissions, and access duration. The project then appears in its origin server's section for authorized users.

To manage access or connect servers, open Preferences → Federation.

👥 Project meeting and minutes

The project’s Team list shows everyone authorized to access it and indicates who is online. The Meeting button opens the shared conversation attached to that project, even when participants are not online at the same time. Authorized people can read and post in the same thread, including from federated servers.

Messages are timestamped and stored on the server hosting the project. Each exchange is also recorded in Compte rendu de la Réunion.txt inside a folder at the project root. Authorized participants can vote to approve or reject shared media. The media card gets a green outline when approved and a red outline when at least one participant rejects it; each person’s latest vote counts. Each shared media item also has an 📝 Annotation drawer for a dedicated discussion thread. Annotations show their author and timestamp and are shared with authorized federated participants.

In the meeting window, choose ⬇ Text for the conversation and vote summary, or 📄 Illustrated PDF for a landscape edit notebook with a large thumbnail and a side panel showing the decision, file location, and voter names. ✉ Send by email lets you enter recipients, a subject, and a message. The text and PDF exports include media annotations; the illustrated PDF adds a timestamped annotation section for each media item. The PDF is attached with an automatic “Sent via Dailies Delivery” signature. The sender is automatically copied (their account must have a valid email address), and the email includes its send date and time. The server’s SMTP settings must be active.

The minutes file is stored inside the project folder, so backups that include that folder can preserve it. Access to the conversation and download follows the project’s access permissions.

🔴 Federated Library

For resources reused across studios—logos, reference photos, brand guides, or templates—an administrator can publish one folder from Preferences → Federation → Federated Library. The feature is disabled by default.

People on authorized servers can browse and download resources in read-only mode. They cannot edit or delete files through federation; the folder stays at its original location and is not copied. Disabling the feature or removing a server revokes its access. With Docker, the folder must be available inside the application container; a read-only mount (:ro) is recommended.

Secure connections between servers

Federation exchanges to an Internet-accessible address require HTTPS. Certificates trusted by the operating system are verified automatically. For a self-signed certificate, verify its SHA-256 fingerprint through an independent channel before trusting it in Preferences → Federation. Network redirects are refused so signatures and enrollment codes are not forwarded to another address.

HTTP remains available only for local or private network addresses, to support internal deployments. The Require TLS setting can also force HTTPS on a private network. Federation audit and health status record configuration changes, certificate approvals, and failed connections.

Update Federation files

On native installations, an administrator can open Preferences → Assistance → Update, review the differences from the Master+Dailies server, then install and restart. The package is signed with the Master key and every file is verified before installation. Replaced files are backed up under .dailies-delivery/runtime/federation-update/backups/.

This updates the application files tracked by Federation, including the native launcher; dependencies and the operating system remain managed by the usual update scripts. Older versions that do not yet have this feature need one manual update first. Docker installations continue to update through their image.