Match responsibilities to actual permissions.
The four role names illustrate responsibilities, not preset grants. Actual access combines role/direct grants with tenant, branch and record scope.
01/05
Team shelf
Compare illustrative role plans.
Fictional menus and daily tasks are neither real role switching nor access acceptance. A broader grant from another role is not automatically narrowed; check effective grants per resource and operation.
Selected role · Managing partner
Management summary within granted scope
Selected role · Lawyer
File, calendar and AI together
Selected role · Assistant
Intake, appointments and document flow
Selected role · Accounting
Invoices, expenses and collection on one screen
App · Role view
Illustrative responsibilitiesManaging partner
Three jobs of the day
- 1/3Looks at the case distribution, the collection rate and overdue invoices on the dashboard.
- 2/3Assesses eligible invitations, role grants and company membership separately.
- 3/3Reviews the weekly firm or branch report and adjusts a role's permissions if needed.
Lawyer
Three jobs of the day
- 1/3Separately changes stages for cases within write and record scope.
- 2/3Checks today's hearing and the coming statutory deadlines on the agenda.
- 3/3Writes the post-hearing note into the file and adds the document to the case.
Assistant
Three jobs of the day
- 1/3Logs the incoming enquiry, assigns it to a lawyer and runs the conflict search.
- 2/3Reviews appointment suggestions, recognising that save checks do not cover every external calendar.
- 3/3Uploads newly arrived documents to the right case.
Accounting
Three jobs of the day
- 1/3Reviews time and expenses, then prepares invoice lines separately.
- 2/3Checks invoices marked Overdue and the status of online payments.
- 3/3Enters expenses per case and looks at the expense summary at the end of the period.
Managing partner
02/05
Role ledger
Four roles, four days
Role names are responsibility plans; choose operation grants and record scope separately.
- 01/04
Managing partner
An authorised user reviews case/finance summaries within permission and record scope; the role name neither opens them nor excludes other roles. Invitations are separate operations, not delivery guarantees. Enabling company MFA policy requires authority and prior actor enrollment; it does not enroll other users automatically.
- Firm-wide reports and KPIs
- Custom roles and permissions
- Finance summary and collection rate
- 02/04
Lawyer
Distinguish case reads from writes. Assigned-case reading alone grants no kanban move, note or document write and does not narrow full reading held elsewhere. Tasks, agenda and documents retain their own grants and record scope. AI requires entitlement, company approval and provider conditions; the draft guide distinguishes fictional examples. UYAP is in preparation.
- Kanban within granted scope
- Deadlines, agenda and tasks
- Mobile file access; UYAP in preparation
- 03/04
Assistant
Intake, appointment and document operations require separate grants and scope. Intake records are neither automatic conflict approval nor client conversion. Matching is limited to accessible client candidates; the guide separates professional decisions. Document sharing creates a link, not delivery or verified client identity. The Assistant name does not revoke finance grants from other roles/direct assignments.
- Enquiry intake and conflict search
- Appointment scheduling
- Separate document and finance grants
- 04/04
Accounting
Invoice lines are entered manually; time/expense records or billable flags do not automatically create invoices. Assess fiscal applicability separately. E-documents and iyzico collection depend on authorised tenant provider connections and required data; queuing or opening checkout is not approval. Read the collection guide. The Accounting name does not revoke other case/client grants.
- Invoice states and conditional overdue processing
- Expense and time entries
- Online payments, e-invoice and e-archive
03/05
Working together
The team looks at the same board.
Kanban shows accessible cases/stages; cards contain number and court. Moving requires separate authority and writable tenant access. Safe case activity differs from technical audit; simultaneous refresh of every team screen is not promised.
Notifications for defined reminders/events depend on current grants, preferences, contact consent, quota and provider/device conditions. Creating a record is not delivery on every channel. Team removal differs from company membership removal; membership changes can affect account-wide sessions.
Distinguish branch scope from team organisation; team membership alone creates neither a case ACL nor a team report dimension. Switching existing company memberships is supported; this page defines no new method for adding an existing account to a second company.
04/05
Professional fact sheet
Plan scope and pricing
Price and limit information cannot currently be verified. Contact us for current terms.
- Plan
- Professional · Price and limit information cannot currently be verified. Contact us for current terms.
- Annual billing
- Price and limit information cannot currently be verified. Contact us for current terms.
- Limits
- Check the plan comparison for current user, case and storage limits.
- On top of Starter
Check current plan terms for feature scope; UYAP is in preparation.
- Branches and teams
Branch access, team organisation and supported report dimensions are separate.
- Multiple companies
Switch existing memberships; no new multi-membership provisioning method is defined here.
- Data import
CSV/XLSX mapping, preview and explicit approval for client/case/invoice/time targets. Data migration guide
- Vekilaw AI
AI use depends on current entitlement/quota, company approval and provider conditions.
- A larger team
The Enterprise plan for larger teams; users, API and service terms are defined in the proposal.
05/05
Questions
What do law firms ask?
- 01/07
How many users can I add?
User limits are defined by current plan terms. Compare user, case, storage and feature scope for your team size; the Professional or Enterprise name alone does not imply a fixed or unlimited allocation.
- 02/07
Does the assistant see invoices?
Review effective finance grants and record scope. The Assistant name alone does not deny access; other role/direct grants combine.
- 03/07
Are branches reported separately?
Reports use supported branch/lawyer/period scope; team membership is not an automatic report dimension. Report, source-read and plan grants are separate prerequisites.
- 04/07
How do we move our existing data?
CSV/XLSX import supports client, case, invoice and time targets through mapping, preview, explicit confirmation and background outcomes; it is not document-file migration. Onboarding tasks prove neither automatic bulk creation nor invitation delivery.
- 05/07
How do files in UYAP reach the system?
The UYAP connection is not yet available. Automatic imports, e-signature setup or inclusion in a specific plan are not promised before the connection method and provider are validated. See the UYAP guide for concepts.
- 06/07
How are login and data kept safe?
Distinguish account MFA enrollment from company policy. New content requires a clean scan before storage, not a guarantee of detecting all malware. Verify backup/recovery, hosting and processing location with actual operational evidence. Review security scope.
- 07/07
Does the invoice show VAT and withholding tax?
Invoice arithmetic uses supported line/tax inputs, with separate applicability review. E-documents depend on an eligible tenant provider, document kind and complete data. Queuing or Sent status is not fiscal/recipient acceptance; payment state follows verified provider results.