Organization isolation
Each organization has its own workspace and dedicated subdomain, with navigation state cleared when users sign out or switch organizations.
The right context for
the right people.
Cohertia structures access around organizations, practices, roles, and matters so teams can collaborate without exposing unrelated work.
Practice-scoped access
Practice Leads and Project Managers receive approved capabilities only within the practices assigned to them.
Permission-checked actions
Sensitive actions are governed server-side as well as in the interface. Hidden controls are not the security boundary.
Boundaries that follow the work.
Controls apply from the organization workspace down to each practice, matter, action, and proposed change.
Organization context
Dedicated workspace routing and validated organization membership keep incompatible sessions and navigation state apart.
Server-side enforcement
The same permission policy governs what a person can see in the interface and what the server will allow them to change.
Financial access
Financial views and matter-level financial fields are limited to approved roles and assigned practice scope.
Source-connected records
Document-derived proposals retain their originating document, page, extraction time, and review state.
Assistance without silent authority.
Cohertia separates model- or rule-derived proposals from the authoritative record until an authorized person decides what happens next.
Minimum context
AI-enabled requests are designed around permitted schema and the context needed for the task—not unrestricted workspace data.
Human review
Reviewers can edit, approve, reject, defer, or dismiss proposed values before they affect a matter.
Decision history
Reviewer identity, status transitions, edits, and source evidence remain available after resolution.
Authoritative separation
Pending proposals do not alter filters, dashboards, financials, or workflows.
Stronger checks when
the device is new.
Cohertia supports authenticator-app verification for new-device sign-ins, with trusted-device management and recovery controls in each user’s settings.
New-device MFA
When an organization enables the policy, a new browser must complete authenticator verification before it can access Cohertia.
Trusted devices
Users can see trusted browsers, revoke one device, or revoke all other devices without waiting for an administrator.
Recovery controls
Recovery codes are generated at enrollment and tracked so users know when they need replacement access options.
Authentication audit
Enrollment, verification, and trusted-device security events are recorded to support accountable access management.
Control without friction.
Least necessary access
Views and actions are scoped to the signed-in user’s current organization and approved responsibilities.
Human confirmation
Document-derived suggestions remain separate from authoritative records until reviewed.
Auditable history
Proposal sources, reviewers, decisions, and edits remain available for accountability.