Integrations
Use this page when you need to know what external system support exists today and what still needs to happen outside Torrens.
Before you start
Section titled “Before you start”- Treat integrations as support for practitioner work, not as a replacement for review or approval.
- Keep external dependencies visible until they are actually complete.
- Use existing firm processes where a connection is not available.
Legal practice management systems
Section titled “Legal practice management systems”Current support: Coming later.
Use your firm’s current process for duplicate entry, system alignment, and external file updates.
Microsoft Outlook
Section titled “Microsoft Outlook”Current support: Coming later.
Torrens can support communications work where the product exposes it, but mailbox-side sending, follow-up, and context still sit with the team unless a guide says otherwise.
Microsoft Word
Section titled “Microsoft Word”Current support: Coming later.
Document preparation, external formatting, and finalisation still rely on existing firm practice unless Torrens provides a specific document workflow for the Transaction.
API access
Section titled “API access”Current support: Coming later.
Partner API setup and endpoint guidance are coming later. Internal foundations exist, but there is no supported onboarding guide yet.
Check before you continue
Section titled “Check before you continue”- Integrations do not remove lawyer review where legal effect is involved.
- External systems remain the place where their own actions happen.
- Do not record an external confirmation as complete in Torrens until it has happened.
What happens next
Section titled “What happens next”Use What Torrens supports today for the current support summary.