Projects

A project is the cross-source matter workspace in Ordalie: it brings together everything that belongs to the same matter, even when the material lives in different places.

In legal work, a matter rarely lives in a single folder. There are internal documents, email attachments, SharePoint or OneDrive files, assistant conversations, and sometimes several rounds of analysis. A project brings these pieces together without moving them.

Think of it as an organization layer above your existing sources. Files stay where they are. Ordalie keeps references to them so you can return to the complete matter faster.

An Ordalie project view grouping the documents and actions for a single matter.
Projects are the preferred workspace for durable matter organization. Tags may still appear in Bibliothèque/Library for lightweight classification and @tag-name mentions, but projects are the better choice for matters that combine documents, external files and conversations.

When to use a project

Create a project when you are working on a matter, transaction, audit, client, or topic that will last beyond a one-off search. The project becomes the natural place to return to: it contains the relevant material, useful conversations, and connected sources.

Avoid overly broad projects such as “Contracts” or “Tax”. Search, filters, or favorites are usually better for those cases. A good project has a clear scope: “Martin matter”, “Supplier audit 2026”, “ACME dispute”, “SNCF Connect acquisition”.

What a project can contain

A project can mix several types of items: Ordalie documents, assistant conversations, analyses, external files, and connected folders. That is the point: it is not tied to a single source.

For example, the same project can contain a contract imported into Ordalie, a SharePoint folder, a conversation where the assistant produced a summary, and a OneDrive file received from a client. The project does not copy anything; it creates a shared working view.

Permissions and sharing

Sharing a project lets organization members work from the same matter space. But a project never replaces the permissions of the items inside it.

Sharing a project does not automatically grant access to every referenced document or file. Each item keeps its own permissions.

In practice, someone may see a project but not see some of its items if they do not have access to those documents, conversations, or external sources. This prevents a project from becoming an accidental shortcut to sensitive content.

With the assistant

Projects are especially useful when working with the assistant. Instead of attaching every piece manually, you can start from an existing project and build the working context from there.

This works well for matter analysis, contract comparison, document audits, and multi-document workflows. The cleaner the project, the more coherent the assistant context.

Migration from tags

Non-favorite legacy tags are progressively converted into personal projects. When several tags match the same name, they are merged to avoid duplicates.

This migration does not delete documents and does not change permissions. It simply turns the former classification system into one better suited to cross-source matters.

Practical summary
  • Use a project for a matter, client, transaction, or audit.
  • Add useful documents, conversations, and external sources.
  • Keep favorites for personal shortcuts.
  • Share the project when several people work on the same matter.
  • Check permissions separately for sensitive documents.
    • Quick difference with a folder

    A folder is a location inside one source. A project is an Ordalie view that can reference items from several sources. One project can therefore include a SharePoint folder, an Ordalie document, and an assistant conversation.

    Dernière mise à jour le 1 juin 2026