Know who can access the work and approve it.
Projects, documents and financial requests need clear access and review rules. Here is how those controls fit into Severus, and what to discuss before a rollout.
Last revised 26 September 2026
Accounts and workspace access
Protected workspace pages require a signed-in account. Workspace roles determine access to records and actions. Administrators invite team members and manage their roles. Multi-factor enrolment and recovery options are available in the product.
Reviews and decisions
Define the review steps for a request and who can approve it. For example, an expense can need a manager’s review before it goes to finance. Approval and activity records help your team follow the decision.
Snape and connected tools
Snape is designed to work through configured workspace permissions and approval steps. Review its sources, drafts and proposed actions. Connecting an external tool does not remove the need to configure access or required approvals.
Files and payment records
Production web traffic uses HTTPS. Supporting documents and recorded provider responses stay with workspace records. A payment status reflects the response from the configured provider; a recorded action is not a promise that it can be reversed.
Requirements for your organisation
Contact us about hosting location, storage encryption, backups, retention, subprocessors, recovery and incident response. These details and any service commitments depend on the deployment and need to be documented in your agreement. This page does not claim a security certification.
Report a vulnerability
Email security@severus.ng privately. Include enough detail to reproduce the issue, without live credentials or unnecessary customer data. The contact is also available in security.txt.
For data handling and requests, read the privacy notice.