Access, automation and financial authority should never blur into one another. Cyntrova is designed to keep the workspace scoped, the decision reviewable and the person responsible visible.
01Business-owned accessInvitations and assignments stay deliberate.
02Human-authorised postingPreparation is not financial authority.
03Tenant-scoped workflowsFirm and client context is checked.
04Traceable actionsRelevant events retain actor context.
01 / WHAT WE CAN STATE TODAY
Trust begins with precise language.
This page separates product controls from operating practices and deployment details. It does not turn intent into a badge, or a configured option into a universal promise.
IMPLEMENTED PRODUCT CONTROL
Enforced in the application path
Examples include verified sessions, active membership checks, role permissions, client assignment and review-state requirements.
PUBLISHED PRACTICE
How we say the service is operated
Privacy, security and service responsibilities are described in Cyntrova’s current published policies and terms.
CONFIRM FOR YOUR DEPLOYMENT
Configuration can matter
Retention, backup, recovery, provider region and integration details should be confirmed for the environment and plan you will use.
02 / ACCESS FOLLOWS RESPONSIBILITY
Connection does not mean unrestricted access.
A verified identity is only the first gate. Cyntrova also evaluates the active workspace membership, permission and—where relevant—the assigned client context before allowing a protected action.
WORKSPACE AUTHORITY
The right person. The right context. The right action.
Workspace administrators control invitations, roles and assignments. A CA or team member does not receive blanket access merely because a working relationship exists.
CA ACCESS BY CONSENTActive membershipAssigned contextGranted permission
01
Roles & permissions
Capabilities are represented as explicit permissions, including separate rights to view, review, approve, post, reverse, export or manage.
02
Client assignment
Non-owner access can be limited to selected client workspaces. Requests outside the active firm or permitted client context are denied.
03
Denied access is evidence
Permission and tenant denials can write audit events with the request, actor, workspace, resource and reason context.
03 / THE FINANCIAL AUTHORITY BOUNDARY
Automation prepares. Authority approves.
Cyntrova keeps interpretation, deterministic calculation and financial approval as distinct responsibilities. The exact approval controls available depend on the workflow.
01IDENTITYVerified session
Invalid, expired or revoked access does not pass the first boundary.
02AUTHORITYRole & permission
The requested action must exist in the member’s granted capability set.
03CONTEXTFirm & client scope
The resource must belong to the active, assigned workspace context.
04DECISIONHuman review
Where an approval control is presented, an authorised user makes the decision.
AI INTERPRETSRULES CALCULATEPEOPLE APPROVEAUDIT CONTEXT REMAINS
THE PRINCIPLE
Automation can move faster. Authority should remain deliberate.
04 / TENANT ISOLATION & AUDITABILITY
A boundary checked at the request.
Cyntrova’s protected API paths build a trusted request context from the user, firm, role, permissions and optional client assignment. Access is denied when that relationship cannot be established.
01
Tenant-scoped requests
Firm membership and active status are checked before the request receives a trusted Cyntrova context.
Active user and firm
Active membership
Permission for the action
02
Client-level separation
Where work belongs to a client, the request can be checked against firm ownership and the member’s client-access mode or assignment.
All, selected or no-client access
Cross-firm client IDs rejected
Business-client context required
03
Traceable events
Audit records can retain who acted, in which firm or client context, on what resource and when—plus request and before/after evidence where supplied.
Actor and role
Action and resource
Timestamp and request context
BOUNDARIES, NOT BARRIERS
Each gate narrows authority to the identity, workspace and action that belong together.
Scope note: audit coverage follows the implemented workflow. This page does not claim that every read, click or infrastructure event is recorded.
05 / AUTHENTICATION & SESSION SECURITY
A session must remain valid to remain trusted.
Protected requests require a valid Cyntrova session. Session tokens are signed and time-bounded; the server-side session record supports verification and revocation.
Signed, expiring sessions
Tampered, malformed and expired session tokens are rejected.
Server-side session state
Session records include expiry and revocation state so continued access can be refused.
Access checked after identity
Authentication does not bypass membership, client assignment or permission checks.
06 / DATA HANDLING & STORAGE
Handle the source with the same care as the books.
Financial workflows can include identity data, documents, transaction evidence, approvals and accounting records. Access should stay limited to the people and services required for the selected workflow.
Configured storage adapters can issue time-limited signed access paths instead of exposing permanent public document URLs.
AI ASSISTANCE
Only the data reasonably required for the selected feature should be sent to the configured provider. AI output remains assistance—not accounting truth.
RETENTION & LOCATION
Ask Cyntrova to confirm the current provider, region, retention, backup and deletion arrangements for your deployment.
07 / OPERATIONAL SECURITY
Security is a practice. Not a slogan.
Production configuration is expected to fail closed when required security settings are incomplete. Customers also share responsibility for credentials, role reviews, supported devices and prompt incident reporting.
CONFIGURATION
Secure defaults need a secure deployment.
Environment controls, allowed origins, provider configuration and release practices must be maintained for the live service.
REPORT AN ISSUE
Found a vulnerability or suspected incident?
Send the affected workspace, time, observed behaviour and safe reproduction detail. Do not include passwords, session tokens or unnecessary financial data.
