Records in lists
Clients, matters, team members, time entries and deadlines each have their own records. Links between them bring the work together under the right client and matter.
Service architecture
Your firm in Lex365.
Your firm in Lex365.
Your information in SharePoint.
Lex365 brings SharePoint into your legal workflow: it organises your firm's information and presents it in a workspace designed for lawyers.
Client records, matters, time entries and deadlines are stored in SharePoint lists. Documents and internal knowledge are held in libraries within the same Microsoft 365 environment.
Lex365
The workspace where you view matter files, manage documents and record your work.
Connection to Microsoft 365 services
Microsoft Graph
Your firm's SharePoint
Lists
Clients, matters, time entries, deadlines and settings.
Libraries
Matter documents, templates and draft documents.
Sign in with your organisation's Microsoft account through Microsoft Entra ID.
Microsoft 365 within Lex365
Your daily activity helps you recall your work.
An email sent, a document reviewed or a Teams meeting can help you reconstruct the work carried out on a matter.
When recording time, Lex365 shows activity captured from Microsoft 365. You can review the day, filter by activity type and time, and use that information to prepare your time entries.
You stay in control of the record
Captured activity serves as a memory aid. The lawyer selects the matter, describes the work and enters its duration before saving the entry.
Emails
References to sent messages and messages marked as read help you recall client contact and communications.
Modified documents
Document activity helps you identify files you worked on and connect them to the relevant clients and matters.
Teams
Meetings, calls and chat activity help you recall conversations, working sessions and contact with your team.
Calendar
Microsoft calendar events provide context for the day's meetings and appointments.
Available integrations depend on your Microsoft 365 configuration and the permissions authorised by your organisation.
In practice
From daily activity to a time entry.
After reviewing a contract, sending an email and meeting a client on Teams, you have references to help you record the work.
- 01
Review your activity
Choose a day and review captured email, document, Teams and calendar activity to recall what you did.
- 02
Record your work
Select the matter, describe the work and enter the time spent based on your review.
- 03
Save to the matter file
The time entry is saved in SharePoint, linked to the team member and matter, and can be viewed in the client's context.
For IT managers
An architecture connected to your organisation's Microsoft environment.
Lex365 is a React web application. It uses Microsoft Entra ID to authenticate users and Microsoft Graph to communicate with SharePoint and authorised Microsoft 365 services.
SharePoint as the storage layer
Operational data and files are stored in the SharePoint site configured for the installation. Lex365 provides the screens, links between records and rules for using that structure.
- Identity and access
- Access uses the Microsoft account in your organisation's tenant. The application authenticates through MSAL and uses delegated permissions for Microsoft Graph operations.
- Data structure
- SharePoint lists store entities and relationships between clients, matters, team members, time entries and deadlines. Libraries store documents and knowledge resources, with folders and metadata.
- Installation and maintenance
- The installation module prepares and updates lists and libraries in the configured site, manages migrations and displays the status of operations.
- Authorised integrations
- Mail, calendar and Teams are accessed through Microsoft Graph. Each source's availability depends on tenant permissions, consent and policies.
- What is accessed in email
- Activity capture uses message metadata. The suggested date for read emails uses the message's last modification time, which may change following other actions; it is a reference for reviewing activity. The integration described accesses metadata without reading message bodies or attachments.