Outside counsel's file shows up on the department board.
Outside counsel is not an automatically restricted role. Assess assigned-case reads, other operation grants and tenant/branch/record scope separately. The API is read-only; webhook test dispatch is separate, and automatic delivery is optional for a selected branch.
Department fact sheet
- Outside counsel
- Assigned files onlyRestricted role
- Department KPIs
- Average case duration, collection rate, upcoming deadlines
- Webhook and API
- Read-only API; signed webhook test and optional automatic delivery
- Service level
- 99.9% availability target; service terms are agreed separatelyContractual
- Plan
- Enterprise plan; current price on the pricing page
Outside counsel and the internal team work on one file.
This illustration is a fictional needs plan, not a preset outside-counsel role or actual ACL acceptance. Assigned-case reading grants no writes, does not narrow full reading from another role and does not automatically close client/finance resources. Company membership removal differs from team removal and can affect account-wide sessions. Documents/notes retain their own grants and record scope.
Illustrative department summary
Fictional indicator headings
Open files
Split by status
Upcoming deadlines
Verify triggers/procedure separately
Average case duration
Created/closed dates of visible closed records
Collection rate
Ratio of visible Paid invoice amounts
| Case no. | Responsible | Status |
|---|---|---|
| 2026/42 E. | Outside counsel | Hearing approaching |
| 2026/58 E. | In-house lawyer | Awaiting notification |
| 2025/311 E. | Outside counsel | Judgment |
Illustrative outside-counsel needs
2026/42 E.
Outside counsel role- Assigned fileNeeded in this plan
- Separate document readNeeded in this plan
- Separate hearing/note readNeeded in this plan
- Client recordsNot needed in this plan
- Financial dataNot needed in this plan
Validate webhook setup with a test dispatch.
The flow below describes a signed test dispatch initiated by an authorised user to a configured address; it is not proof of real delivery. Automatic delivery is enabled separately for a selected branch; ERP record creation is not offered.
Address configured
Illustrative test flow; not real delivery
Address setup
Test addressTo be reviewed
Test request
Test addressIllustration
Test dispatch
Test addressConditional
Recipient response
Test addressTo be validated
Test result
Test addressDraft
The access of in-house and outside counsel is written in the matrix.
The table is a fictional responsibility plan, not preset grants or a measurement of the most common setup. Role/direct grants combine; verify each resource scope separately. Technical audit covers supported writes, not a complete person-level history of every read/download. Account MFA enrollment and company policy are separate operations.
| Area | Department head | In-house lawyer | Outside counsel |
|---|---|---|---|
| Assigned files | needed | needed | needed |
| Other files | needed | needed | not needed |
| Client records | needed | needed | not needed |
| Documents (in the assigned file) | needed | needed | needed |
| Hearing notes | needed | needed | needed |
| Finance and invoices | needed | not needed | not needed |
| Reports and KPIs | needed | not needed | not needed |
| User and role management | needed | not needed | not needed |
The report you hand to management comes out of the file.
Dashboard indicators come from separate reads, not one atomic snapshot. Average duration uses creation/closure of visible closed records; collection ratio uses visible Paid invoice amounts and is not bank reconciliation. Four report families use supported date/branch/lawyer dimensions plus source-read, report and plan grants; no universal client/case filter or automatic management presentation is promised.
The Enterprise plan sheet.
- Plan
- Enterprise plan; current price on the pricing page
- Users and storage
- Check user and storage limits in current plan conditions
- Support
- Verify support channels, priority and times in written terms
- Service level
- 99.9% availability target; written service and measurement terms are agreed separatelyTarget
- Isolated environment
- Assess isolated-environment requests and scope separately; this is not acceptance of an available deployment
- Integration
- API scope is read-only access, webhook setup, signed test dispatch and optional automatic event delivery. Check plan terms; UYAP is in preparation.Webhook and APIUYAP integration
- Training
- Training scope and schedule are agreed separately in writing
- 01/03 Demo
- Demo scope and schedule are arranged separately
- 02/03 Pilot
- You try your real workflows with a team of your choice in a trial account.
- 03/03 Rollout
- Verify written scope, providers, user grants and acceptance steps separately
Vekilaw is developed and operated by . ISO/TSE certificate details have not been published.
What do legal departments ask?
- 01/07
What is the isolated environment?
An isolated environment is a request/assessment topic; this page attests no available deployment, dedicated infrastructure or included plan service. Technical scope and written terms are determined separately.
- 02/07
What data can outside counsel see?
The outside-counsel name does not narrow access automatically. Assigned-case reading is a separate opt-in grant and does not narrow full case reads held elsewhere. Review client, document, note and finance grants/scope separately.
- 03/07
Which data can I reach through the API?
API keys provide read-only access to permitted case, client, hearing, document metadata and invoice data. Write operations or unrestricted document file access are not promised. Webhook setup, signed test dispatch and optional automatic event delivery for a selected branch are available.
- 04/07
How does the contract process work?
Demo/pilot/rollout steps are discussion topics, not accepted schedules or contracts. Plan/service and any isolated-environment scope are assessed separately in writing. Review the terms.
- 05/07
What do the audit records keep?
Tenant/branch and record access are enforced server-side; anonymous document sharing is a separate link/password path. Technical write audit is not a person-level history of every access. Assess MFA through account enrollment and company policy.
- 06/07
Which indicators can I present to management?
Dashboard indicators come from separate reads, not one atomic snapshot. Average duration uses creation/closure of visible closed records; collection ratio uses visible Paid invoice amounts and is not bank reconciliation. Four report families use supported date/branch/lawyer dimensions plus source-read, report and plan grants; no universal client/case filter or automatic management presentation is promised.
- 07/07
Can webhook deliveries be traced?
The result of a signed webhook test dispatch initiated by an authorised user, and of automatic delivery attempts, can be reviewed in the integration log. This does not prove that the recipient completed an ERP operation; delivery is at-least-once and the receiver must deduplicate.