Activity
Last updated: November 20, 2026
The Activity group gives you cross-module views. Instead of opening one record at a time, you see everything of a kind across all the records you can access. Each view respects your permissions, so you see only what you’re allowed to.
Calendar
An aggregate calendar of every event on records you can access, each labeled by its record and module. The header’s Filter button narrows it by Modules, Notifying me, or Organization, so you can focus on upcoming deadlines across your portfolio. Filters last for the visit only.
Attachments
A single, filterable list of every attachment you can access, with columns for Attachment, Record Type, Record, Files, and Description. From here you can select attachments to download together as a ZIP. Deleting them in bulk is for Editor users, and only for attachments in modules they edit.
Workflows
All the workflows you’re a participant in, filterable by status, due date, and module. This view also has a New request button for starting an authorized request workflow. To work through a workflow once it has started, see Working on a Workflow.
Reports
A report is a saved, reusable question: pick its record type (the Anchor records setting), then choose the columns to show — including fields from related records, counts or totals across related records, and a record’s current timeline status. Run it whenever you want a current answer. Results land in a grid you can sort, filter, and export to CSV.
Reports are shared across the subscription, not personal to whoever built them. Anyone holding the reporting role can see and run every report, and a report is itself a record — editable, trashable, and restorable like any other. Reports are available on Business and Enterprise plans, and require the reporting role, granted per person by an admin to any member except guests. A report built on a module that later gets disabled drops off the list rather than erroring, and reappears if the module comes back.
Building and saving a report
Click New on the Reports page to open New Report. Type a Report name, pick the Anchor records type, which is the kind of record each row stands for and which controls the related fields you can add later, then click Save. The new report opens with some starting columns, and the Edit drawer is already open so you can shape it. Rename the report later from that drawer.
Use Edit to shape the columns. Their order in the list is their order in the grid, left to right, so you can reorder them by dragging, in the list or in the grid. Click a column’s header to rename it, or remove the column. Under each column Lextree shows the path its values come from, for example “Owner › Legal Entity › Legal form”. To add a column, use Add column. Its From list is optional and names the relationships the report can reach, and Add field is a searchable list. Leave From empty and Add field shows every available field along with its source. A field is added as soon as you choose it, and From keeps its setting, which makes it quick to add several fields from one source. A field the report already has doesn’t show up in the list again.
When a record can point to either a person or an organization, for example an ownership stake’s owner or a matter’s counsel, one column shows whichever applies, and you can add a Type column alongside it. If a column draws from a module that is disabled, it drops out of the grid and the CSV but stays in the Edit list, with a note naming the module that hides it.
A report keeps nothing you change until you click the header’s Save. That covers its name, its columns, and the filters, sorts, column order, and column widths in its grid. Save lights up when the report differs from the saved version, and the notice Unsaved changes — click Save to preserve them. stays up until you save. If you leave the page first, the changes are lost. A saved change applies to every reporter, since the report belongs to the whole subscription. To try a variant without touching the original, click Copy, which opens a new report titled Copy of … that starts with the same columns and layout.
Export gives you a CSV, named after the report, of what the grid shows at that moment: the columns in their current order, with the grid’s filters and sorts applied. Delete sends the report to the trash. On plans with API access, an API key can also read, run, and edit reports; see API access.
The reporting role’s reach
A report reads across every enabled module, regardless of the reporter’s own module permissions or any record restriction — in practice read access to the whole subscription, restricted records included. That reach is deliberate: a renewals report with holes in it would be worse than no report at all. It also means the role is worth granting carefully. See Access for how per-person roles are assigned.
Reports versus your list pages
Every list page is already a live, personal, single-module view — save grid settings, star favorites, export to CSV — available on every plan. A report is the saved, cross-module, shareable version of that same idea: Business and Enterprise plans add Reports on top of what list pages already offer. See Working with Grids for the list-page side of that comparison.
Trash
Deleted records and attachments go to Trash rather than disappearing at once. If you delete something by mistake, restore it from here.
How cascading works
Trashing, restoring, and permanently deleting a record all cascade through its related records. Trash a record and its related records disappear with it — trash a board and its meetings vanish too, even though nobody touched them. Restore it and everything comes back together. Permanently delete it and its related records are permanently deleted too. Other than restoring the trashed parent, there’s no way to regain access to the records that went with it.
Partial restores and deletes
A related record that was already trashed on its own is left out of a parent’s restore — bringing it back would put it on a list it can no longer legally appear on — so it stays trashed, now alongside its restored parent, rather than being silently un-trashed. Deleting several organizations or people at once can also come back partial: records nothing else references go to Trash, records still referenced by something else stay put, and a message names how many were kept and what references them.
Deleting forever
To remove something for good, select it on the Trash page and click Delete forever. Like deleting itself, this is an Editor action. Before anything goes, Lextree opens a Delete forever? dialog that warns the deletion can’t be undone and lists what would go: the number of Records you selected, how many Nested records sit beneath them, and how many Attachments are on them. The nested-record and attachment counts appear only when there are some. Organizations and people that other records still reference can’t be deleted yet. They are listed as kept, and the button changes to Delete N forever, with N the number that will go. The same button and dialog work on the trash pages for calendar events, workflows, attachments, reports, and charts.
Storage and permanent deletion
Trashed files still count toward your storage — trashing frees nothing. A permanent delete, or the trash retention period running out, frees the storage a file uses. See When storage is full for what happens at your plan’s limit.
Two removals skip Trash entirely and become permanent the moment you save: removing an entry in Edit Timeline (see Timeline), and removing an individual file from inside an attachment’s Current Files.