Changelog

Setting up an insight with many columns just got a lot faster. Upload an Excel file with three columns — Label, Prompt, and Column type — and each row becomes a new column in your insight, ready to extract data from any case.

Define everything once in a spreadsheet, drop it in, and you're done. Supported types include shorttext, date, list, and the rest you already use. Only column definitions are imported, never row data, so the same spreadsheet works as a reusable template across cases and matters.

Available now in any insight. .xls and .xlsx supported.

You can now use oval-based stacked and double shapes in your structures - the same layout patterns you know from stacked and double rectangles, now with ovals.

Four new shapes are available in the shape picker under the stacked shapes section:

• Stacked Ovals - three layered ovals, offset diagonally

• Stacked Ovals (Flipped) - same pattern, mirrored direction

• Double Ovals - two layered ovals, offset diagonally

• Double Ovals (Flipped) - same pattern, mirrored direction

All four shapes are fully supported in PowerPoint exports.

Previously, undo and redo were disabled when mirror mode was active - any changes you made across slides couldn't be stepped back. That's now fixed.

When you edit, move, resize, create, or delete elements in mirror mode, every mirrored slide is included in the undo/redo stack. One undo reverts the change everywhere - no need to manually fix each slide.

The sidebar has been rebuilt around the idea of scope — the workspace, group, or matter you are currently working in. Navigation, dashboards, and the create button all adapt to where you are, so you stop bouncing between unrelated context every time you click a link.

What is new

• Scope selector at the top of the sidebar lets you pin Juristic to your whole workspace, a specific group, or a single matter.
• Context-aware menu links resolve dynamically — My work, My groups, Dashboards and the AI entry now point to the right place based on the active scope.
• Pinnable menu items with per-user overrides, plus organization-wide menu defaults so admins can decide which items every user sees pinned by default.
• Redesigned sidebar footer: a Help popper with knowledge base + changelog links, an Admin / App toggle button, and a refined user profile menu with avatar and email.
• Collapsed mode keeps the sidebar narrow and surfaces sub-menus through a popper, with hover tooltips on the scope selector.
• Welcome onboarding modal introduces the new scope concept the first time a user logs in after the update.

Why it is useful

Most work in Juristic happens inside a matter or a group, but the sidebar previously stayed identical regardless of where you were. Anchoring the navigation to a scope means fewer clicks to reach the dashboards, boards, and AI tools that belong to the case in front of you, and gives admins a way to standardize the navigation across the whole organization.

Matter layouts now follow a clear inheritance chain: organization → group → matter. Configure the experience once at the right level and every matter underneath inherits it automatically.

What is new

• Organization defaults — set the baseline layout from Admin → Organization → Matter layouts. It applies to every matter that does not override it.
• Group overrides — give a specific group its own widget arrangement when its work differs from the rest of the organization.
• Per-matter overrides — matter admins can fine-tune a single matter without touching the rest of the org or group.
• Per-role tabs at every level — edit the Admin, Lawyer and Client layouts independently.
• Reset to inherit — clear an override at any level and that matter falls back to the next layer (group → org → built-in default).

Why it is useful

Legal practices are not flat. A real-estate group needs a different matter view than a litigation group, and a single high-stakes transaction may need its own layout. The new inheritance chain lets organizations set sensible defaults centrally and only diverge where it really matters.

Dashboards can now be owned by the lawsuit or board they belong to. They are still fully featured dashboards — they just live in the right place.

What is new

• Owner scope selector in the dashboard create / edit modal: choose Lawsuit, Board, or leave it global.
• Lawsuit-scoped dashboards appear in their lawsuit's dashboard list and travel with the matter — no more orphan dashboards floating in the global namespace.
• Board-scoped dashboards stay tied to the board they were built for.
• Backwards compatible — existing dashboards without a scope continue to work exactly as before.
• Permission-aware — users without access to the parent lawsuit or board cannot create or list scoped dashboards for it.

Why it is useful

Global dashboards do not match how teams actually think — most analytics belong to a specific case or a specific workflow. Owner scopes give dashboards a home, make them easier to find, and keep the global list focused on dashboards that really are organization-wide.

Sharing a matter with an external client used to mean sharing a workspace, timeline or board separately. Matters now have a first-class external share flow that drops the client straight into the matter's client portal view.

What is new

• External tab on the matter Share popper lists everyone who already has access.
• Invite a new external user with first name, last name, email, phone and country code — phone numbers are normalized automatically.
• Validation is enforced server-side: malformed emails or phone numbers are rejected before an invite is sent.
• Dedicated client view — invited users land on the /client/lawsuits/... route and see only the widgets configured for the Client role.
• Revoke access in one click — removed users immediately lose access to the matter and its data.

Why it is useful

Most matters need at least one external participant — a client, a counterparty, a co-counsel. Giving the matter its own share flow (instead of routing through a board or timeline) means the right person ends up with the right view, with the right permissions, on day one.

Every cell type on a board now supports a default value that is applied to newly created tasks. No more typing the same starter values dozens of times.

What is new

• Default value entry in the column header menu, available across:
• Text — preset string
• Number — preset number, respects the column's number formatting
• Date and Date range — preset dates
• Checkbox — preset checked / unchecked
• Clock — preset duration
• Country — preset country with flag
• Link — preset URL with optional label
• Dropdown — preset option
• People — preset assignee
• Status / Priority / Label — preset label
• Live sync — change a default in one tab and other open boards update over WebSocket without a refresh.
• Validated — the API rejects defaults whose shape does not match the column type.
• Non-destructive — defaults apply only to new tasks, never to existing ones.

Why it is useful

A board is the same shape every day; the same defaults belong on it every day. Configuring them once removes a long tail of small frictions when adding new tasks, and keeps boards more consistent across users.