Role-based access
Define access around a job function and update the people who hold that role together.
Please wait...
RAPTIX security
Security is not a row of badges. In RAPTIX it begins with who can enter a workspace, what each role can reach, and whether every important action leaves a usable record.
Access
A person should not see a sensitive file simply because they can enter the workspace. RAPTIX applies access from the workspace down to a role, a product area, a workflow, a document, a page, or one sensitive passage.
Define access around a job function and update the people who hold that role together.
Keep sensitive processes and files out of view unless a person or role has been granted access.
Apply access to an entire document, a single page, or selected content—hide it, deny it clearly, or mask a sensitive value while the safe context stays visible.
Limit which assistants a person can open and which permitted documents can support an answer.
Teams can use Microsoft single sign-on so work access follows a familiar organizational identity.
Data protection
Every workspace is isolated at the data layer itself, not only hidden by navigation. Passwords, provider keys, and connection credentials are encrypted, access-controlled, and masked after saving.
Each organisation's data is separated at the data layer itself—not only hidden behind navigation and menus.
Passwords, provider keys, and connection details stay encrypted and masked after saving. A team uses the connection without an ordinary user or API response ever exposing the secret.
Custom workflow code runs inside a limited environment that cannot reach the network, stored secrets, or arbitrary files on the host.
Account protection
Sign-in, reset, and session behavior are hardened by default, so opening a workspace does not create an easy target.
Password reset links expire and cannot be reused once they have served their purpose.
A reset request never reveals whether a given email address exists in the workspace.
Signing out invalidates the session on the server, not only the page in front of you.
Repeated automated sign-in attempts and API abuse are throttled before they become a real risk.
If our team ever opens your workspace to help with an issue, the session is visibly marked on screen, blocked from making any change at the server level, and can be ended by anyone with one click.
Traceability
RAPTIX keeps the process history, file versions, comments, decisions, and access events close enough to investigate and clear enough to understand.
See who acted, what they decided, what information was submitted, and how the process reached its current state.
Keep earlier revisions available when a file is replaced or annotated, instead of erasing the context behind a decision.
Administrative, sign-in, permission, application, and document events are captured for review.
AI with oversight
Document assistants are designed to return the source beside the answer. Workflow AI can prepare or route a case while your process keeps the human approval wherever it belongs.
Open the document, page, and supporting passage behind an answer before using it.
Document access rules remain part of what an assistant is allowed to retrieve for a user.
Place a person before or after an AI step and keep the final decision attached to the accountable reviewer.
An honest trust page
This page describes product controls available in RAPTIX. It does not claim SOC 2, ISO, or another third-party certification. If your review needs a specific control, data-handling answer, or current security document, contact us directly.
Start a security reviewCreate a workspace for the requests, documents, and decisions your team needs to keep moving.