Cloud legal software access controls
Cloud Legal Software: Ethical Walls and Conflict Checks
How to evaluate ethical wall controls, conflict checks, automatic group membership and audit logs in cloud legal software, with a buyer checklist.
Direct answer
Cloud legal platforms enforce ethical walls through matter-level restrictions that deny named people, groups, or offices, while conflict checks record who searched which parties and what was decided. Evaluate whether group membership updates automatically from your identity source, whether denies override inherited access everywhere including search, and whether detailed audit logs capture every grant, denial, and access attempt.
How CaseDocker helps
CaseDocker provides matter-level membership, role-based access and activity logs, so only named case members, groups and client members see a given matter and its documents. Per-folder and per-file members add further limits. It does not include a dedicated ethical-wall or conflict-check engine, so those policies and checks remain with the firm.
- Matter-level membershipLimit each matter to its case members, groups and client members.
- Role-based accessAssign roles in the firm and per matter instead of broad shared access.
- Activity logs and file historyReview who opened or changed records through logs and file history.
Definitions
Conflict check
A search of current, former, and prospective clients and related parties, with a recorded decision, performed before a matter is opened or its scope materially changes.
Ethical wall or screen
A set of organisational and technical safeguards that keeps a person or group from information about a matter, applied where the governing professional rules and client terms permit screening.
Deny rule
A restriction that blocks a named person, group, or office from a matter even when other permissions would normally grant access.
Automatic group membership
A mechanism by which people join or leave access groups based on attributes in a directory or HR source, such as office, department, or role, without manual edits.
Matter-level security
Permissions applied to a matter workspace and its content, as distinct from system-wide roles that apply to every record.
Detailed audit log
An attributable, time-stamped record of access, denial, permission, configuration, and export events with enough context to reconstruct what happened.
Screened person
An individual who must be kept from information about a particular matter or client under a screening arrangement.
Inherited access
Permission a user receives through membership of a group, role, office, or parent folder rather than a direct grant.
Directory sync
Automated synchronisation of users and group membership from an identity provider or HR system into the legal platform.
Exception approval
A time-bound, attributable decision to depart from a restriction, with reason, scope, and review date.
Negative test
A test performed with an account that should be denied, to confirm the restriction works across views, search, reports, and integrations.
Practical workflow
Start from the rule, not the feature
Confirm with ethics counsel which screens your jurisdictions and client agreements allow, who must be notified, and what evidence you must keep. Write the access outcomes you need before comparing products, because a feature list cannot tell you whether a screen is adequate.
Connect conflict checks to matter opening
Require a recorded conflict search and decision before a matter workspace is created or content is shared. Capture the parties searched, sources, reviewer, result, and any waiver or screening condition, and link that record to the matter so the access decision has its reason attached.
Test deny precedence across every surface
Check that a deny beats inherited group, role, and office access in the matter list, full-text search, reports, dashboards, notifications, mobile apps, exports, API calls, and integrations. A wall that hides a folder but leaks titles in search or a report has not worked.
Evaluate automatic group membership
Ask how access groups sync from your identity provider or HR source, how quickly changes apply, what happens when a person moves office or leaves, and whether manual overrides are flagged. Stale membership is the commonest reason a screen quietly stops matching reality.
Review audit-log depth and access
Confirm the log records grants, removals, denials, failed attempts, searches, views, downloads, exports, configuration changes, and administrator actions, with actor, target, time, and source. Check who can read or alter the log, how long it is kept, and how it can be exported to your monitoring tools.
Plan exceptions, lateral moves, and emergencies
Define approved ways to add temporary access, handle a lateral hire who brings a conflict, and respond to urgent needs. Each should require a named approver and reason, expire automatically, and appear prominently in the audit log for after-the-fact review.
Check lateral hires and personnel moves
Include a conflict and screening review in onboarding for lateral hires and transfers, and record any resulting restrictions before the person receives access to matters.
Review hosting, tenancy, and data residency
Confirm where data is stored, how tenants are separated, and how support staff of the vendor access customer data, since these affect confidentiality obligations independent of matter permissions.
Define log retention and monitoring
Decide how long audit logs are kept, who reviews them, and whether they feed a monitoring tool, so denial bursts and unusual exports generate action rather than just records.
Run adversarial tests and recertify
Before go-live and on a schedule, test with accounts that should be denied, including administrators and integration users, and keep the results as evidence. Recertify walls whenever matters, staffing, or client instructions change.
Comparison
| Evaluation area | What good looks like | Common weakness |
|---|---|---|
| Conflict check linkage | Searches, decisions, and conditions are recorded and tied to the matter before access is granted. | Conflict results live in email or a separate spreadsheet with no link to access. |
| Deny precedence | Denies override inherited access in views, search, reports, exports, and APIs. | Restrictions hide content in the browse view but not in search or reports. |
| Group membership | Groups update automatically from the directory and flag manual overrides. | Manual lists drift as people move office or leave. |
| Audit logging | Denials, failed attempts, exports, and admin changes are logged and exportable. | Only successful views are logged and logs are editable or short-lived. |
| Exceptions | Time-bound, approved, and visible exceptions with automatic expiry. | Permanent administrator grants with no review. |
| Testing evidence | Documented negative tests are repeated after each change. | Walls are assumed to work because they were configured. |
| Lateral moves | Screening review is part of onboarding, with restrictions in place before first access. | Restrictions are added only after someone raises a concern. |
| Vendor access | Vendor support access to customer data is documented, limited, and logged. | Support access is assumed to be harmless and is not reviewed. |
Limitations and exceptions
- Software can enforce configured permissions but cannot decide whether a screen satisfies professional rules, whether a conflict can be waived, or whether notice or consent is required. Those are legal judgments that vary by jurisdiction.
- Technical walls do not control conversations, paper files, personal devices, screenshots, or memory, so they should be paired with policy, training, and physical safeguards.
- Capabilities such as automatic group membership, deny precedence, and log depth differ by product, edition, and configuration, and should be verified in a hands-on test rather than from marketing material.
- Audit logs can themselves contain confidential matter names and search terms, so control who can read them and how long they are retained, subject to holds and client terms.
- Identity-provider, backup, archive, and integration paths can have separate permission models that sit outside the platform wall and must be included in the test scope.
Primary sources
Methodology
This guide organises evaluation criteria from public professional-responsibility rules and security control catalogues. It does not rank vendors or cite performance figures. Treat the checklist as a structure for a proof-of-concept in which your own ethics counsel and security team define pass and fail results using your matters, identities, and integrations.
Test matter access controls before you rely on them
Reach out and learn more about our offerings and how CaseDocker can help you
Built for legal operations teams
Share your use case and we will connect you with the right team for product guidance, pricing, and rollout planning.
Clear next steps
Expect a response from our team with the most relevant next step for your inquiry.
Send us a message
Get in touch
FAQs
Related CaseDocker capabilities
Legal case management
Control matter teams, documents, and activity history with role and matter-level permissions.
ExploreCompliance management
Track access reviews, exceptions, and evidence for confidentiality controls.
ExploreLegal playbooks
Route conflict decisions and exception approvals through assigned workflow steps.
ExploreTurn this guide into an operating plan
Share your current legal workflow and CaseDocker can map the right modules, integrations, controls, and rollout sequence.
