Projects

Projects are the shell’s matter workspace: documents, tasks, chat, timeline, and collaboration all meet here.

What to expect inside a project

Area	Available in
Documents, Tasks, Timeline, Chat	LEO, VERA, ZIA
Research tab	LEO only
SharePoint link	when your organization has the integration
Partner inbox	eligible LEO partner offices only

Project list

The project list is a card grid that shows projects alongside organization knowledge bases. Rows are clickable; selecting one takes you into the project workspace.

From the project list you can:

• create, open, and rename projects;
• archive or delete them;
• leave a shared project;
• optionally build a project directly from SharePoint.

Product scope

Projects are product-scoped:

• leo and leo-lite share scope leo;
• vera uses scope vera;
• zia uses scope zia.

That means:

• each product shows its own project list (a LEO project is not visible from VERA, and vice versa);
• switching product can change what you see without any data actually disappearing;
• project chats and their caches are also kept separate per product.

Archive vs. delete

• Use Archive when the matter is finished but you still want the project to remain findable.
• Use Delete only when you are sure the project and its related context may actually be removed.

Documents inside a project

Project documents use the same upload contract as Files.

That means project uploads also support:

• standard documents,
• images,
• email files,
• CAD,
• ZIP,
• audio such as .mp3, .m4a, .wav,
• presentations such as .pptx and .ppt.

Use Files as the source page for:

• exact supported extensions,
• processing statuses,
• preview/download/read-text behavior.

Review status per document

The project document table has an optional Review status column. It is hidden by default and can be enabled through Columns.

Review status	Use it for
needs_review	the file still needs a first review
reviewing	someone is actively reviewing it
reviewed_with_notes	reviewed, but still has open points
approved	ready for downstream use
not_applicable	review labeling is not relevant here

Document actions

Per project document you can normally:

• preview it or open it in SharePoint,
• open info/metadata,
• download it,
• start a chat with the file as an @ mention,
• translate it,
• delete it.

Document workspace

Beyond the document table there is a document workspace: a single-screen view where documents, tasks, and chat sit side by side. In LEO this workspace uses a research-aware layout: running research jobs and their sources are surfaced next to the documents so you can move quickly between reading, tagging, and follow-up questions.

Collaboration

Through Share / Invite you can grant colleagues access to the project.

Practical impact:

• project chat becomes shared with project members;
• tasks and review labels are visible to project members;
• if you delete a file from the project knowledge base, it disappears for everyone in that project scope.

SharePoint inside projects

If SharePoint is enabled for your organization, you can connect a project to a site.

When creating a SharePoint project

You can:

• select a site,
• choose top-level folders or the whole site,
• let the import run as a background job.

In an existing linked project

You typically see:

• the linked site URL;
• import status (running / completed / failed);
• whether sync is required;
• a Sync now action when changes are detected;
• an Add folders action when the project is folder-scoped.

What sync does:

• re-ingests new or changed files;
• removes deleted SharePoint files from the project.

Project chat

For matter work, prefer project chat:

• project documents become the main context;
• # mentions for tasks work directly;
• exports are easier to attach back to the matter;
• the same prompt-first chat workspace also drives search, knowledge, prompt library, and (in LEO) research.

Inside project chat you can search conversation content and preview Word attachments directly.

Save a personal chat into a project

From a personal chat, use Save to project in the chat actions to attach the conversation to a project. After saving:

• the chat appears in that project’s history;
• follow-up questions automatically use project context;
• colleagues with project access can open the chat as well.

More: Chat.

Requesting a second opinion (LEO lite only)

This flow exists only inside LEO, for organizations with the leo-lite entitlement. VERA and ZIA have no second-opinion flow.

The requester flow starts from a project.

Requirements:

• your organization has leo-lite entitlement;
• you are the project owner;
• you select one or more partner offices that have both leo and leo-partner.

What the flow does:

1. You open Request second opinion in the project.
2. LEO pre-fills intake fields where it can based on profile and project documents, including:
   • expertise_tags,
   • counterparty_name,
   • deadline_urgency,
   • jurisdiction_region,
   • an initial partner-facing context message.
3. You review and correct that intake.
4. You review ranked partner-office suggestions.
5. You manually select one or more offices and send the request.

Important:

• ranking is advisory, not auto-routing;
• ranking is driven mainly by expertise, with urgency/SLA and jurisdiction used as additional signals;
• counterparty_vat and fee_preference are no longer part of this flow;
• access is only granted after partner triage;
• access is ultimately granted to the assigned user, not generically to the whole partner office;
• revoke/complete removes that external access again;
• the AI case brief only becomes visible after the conflict stage is cleared.

AI case brief

After a second-opinion request is sent, LEO can asynchronously generate an AI case brief.

Typical contents:

• an executive dispute summary;
• key legal questions;
• missing documents or annexes.

Visibility:

• hidden during conflict_pending;
• visible after conflict_cleared;
• kept redacted while a conflict remains blocked.

Partner inbox (LEO partner offices only)

The partner inbox exists only inside LEO, and only for partner offices that receive second-opinion requests. VERA and ZIA organizations do not see this inbox.

The partner inbox is visible to eligible partner offices:

• product leo,
• entitlement leo-partner,
• user role OWNER or ADMIN.

The flow is intentionally split:

Step 1 — conflict check

The partner only sees limited data:

• requesting organization,
• counterparty,
• redacted context.

The partner can:

• clear the conflict,
• block the conflict.

Step 2 — full review

After clearance, the partner sees:

• the full intake,
• the AI case brief,
• assignee selection within the partner office.

Then the partner can:

• assign a colleague and accept the request;
• decline the request.

Notifications for this flow show up on Notifications.