How can we access Portal?
For beta access, contact your Legora representative or send a request to [email protected]. We will help you move onto our new, more secure Global Authentication system and sign a contractual addendum to get started.
Do external client users need to buy a Legora license?
No. External client users access your Portal by invitation and only see the resources your firm shares.
What can we share in the Portal?
You can share:
Projects (and selected project files)
Tabular reviews
Organization databases (Org DBs)
Workflows
Can clients use the Assistant in Portal?
Yes, but the Assistant experience in Portal is scoped down.
It is primarily for searching and asking questions over content your firm has explicitly shared.
It excludes legal research, web search, and other platform capabilities.
Answers are grounded and cited, with links back to the relevant source content.
The Assistant can be used in chat on a shared tabular review, and the context is locked to that tabular review.
Can clients see our workflow prompts or workflow logic?
No. When a workflow is shared with clients, Portal is designed to protect workflow IP.
Clients can see the workflow description and outputs.
Clients cannot see the underlying prompts or workflow logic.
Can clients use their own files in workflows?
Clients can attach shared project files as inputs when running shared workflows.
A workflow run is locked to one project at a time.
Uploaded documents and workflow-generated documents may be marked Private and only accessible to the guest user who created them.
What authentication options are available for Portal guests?
External users log in with email and password.
MFA (via authenticator app or SMS) can be required by the firm admin, either at Portal creation or later.
Why can’t I see Portals in the sidebar?
Portals may be hidden unless you are the Portal creator or have been explicitly invited.
Admins can always access Portals from Org settings.
How does sharing work in Portal?
Portal uses a collaboration policy model.
Permissions are item-specific and not inherited from projects.
Each resource requires explicit sharing.
If we unshare a resource or remove a guest user, what happens?
Access is revoked immediately when the unbroken path from user → collaboration policy → resource is broken.