Database-level isolation
Each organization's records are separated by rules inside the database itself, not only in application code.
Security
Security you can check, entry by entry
Each organization is kept apart in the database. People, API keys and the CFO Copilot see reports and figures only for the companies they are granted. Credentials are sealed, money never moves without a person, and every action is written to a chained audit log. Anything not built yet is labelled roadmap.
Every organization apart, every person in scope
Separation starts in the database and carries through to reports, figures, the Copilot and the API. The audit log is read for the whole organization by those allowed to see it.
Company-scoped roles
Access is granted per company and per role. A finance manager for Egypt sees Egypt: in reports, in figures and in the Copilot.
The same scope in the Copilot
The CFO Copilot answers inside the scope of the person asking, so it cannot reach a company that person cannot open.
API keys as service accounts
Each API key acts as a service account with one role and the companies you choose, and nothing more. A key can never approve, sign off or complete a four-eyes review: those always need a person.
The AI goes through the same doors as your team
The Copilot reads the ledgers through the product's own finance functions, under the permissions of the person asking. It never holds the keys.
No credentials
The AI never receives ERP passwords, API secrets or access tokens.
No open database
It has no open database access. It can only call finance tools that check permissions first.
Figures from the ledgers
Every figure in an answer comes from the ledgers through the product's finance functions, not from the language model.
It says when it cannot answer
When the data cannot support an answer, the Copilot says so rather than guess.
Sealed secrets, and a second check where it matters
What connects Naarvin to your systems is encrypted and never shown again. Sign-in can ask for more than a password, and your organization can require that for everyone.
Sealed connection credentials
Passwords, keys and tokens for your connected systems are encrypted at rest and can never be read back.
Sealed, signed webhooks
Webhook addresses and secrets are sealed too, and every webhook is signed so your systems can confirm it came from Naarvin.
Two-factor sign-in
A passkey (Face ID, Touch ID, Windows Hello or a security key) or a code from an authenticator app at sign-in, with backup codes for a lost phone.
A fresh check before sensitive actions
Sensitive actions ask for a new verification, even inside an active session.
Single sign-on
People sign in through your organization's identity provider.
Single sign-on works over OpenID Connect (OIDC) or SAML 2.0 with signed assertions, and SCIM 2.0 can add, update and deactivate people from your identity provider.
Every action written down, every decision routed
The audit log only ever grows, and each entry carries the fingerprint of the one before it. Approvals follow an authority matrix you set.
Append-only, chained audit log
Entries are only ever added. Each one carries the fingerprint of the entry before it, so a changed or missing entry breaks the chain, and the log can be exported with every fingerprint.
Authority matrix
Amount tiers per action decide who approves what, and the route is fixed when the request is raised.
Segregation of duties
Nobody approves their own request, and each approver decides once.
Payment releaseBudget changeReceivable write-offJournal postingCapital expenditureAsset disposalAccess request
Naarvin never moves money
It prepares the work and a person releases it. Postings to your books wait for approval. Notices to Slack, Teams and webhooks carry no amounts; messages with figures go only to people whose access covers them, or to a customer about what that customer owes.
Payment files, released by a person
Naarvin prepares payment files ready to upload to your bank, paying only supplier bank details that a second person has verified. When you set a payment approval route, only approved bills can go into a payment run. A person uploads the file to the bank.
ERP postings off by default
Posting journals back to your ERP stays off until you switch it on, and each posting passes your approval route first.
Hosting region declared
Settings show each organization the hosting region its installation declares, and which outside services process its data.
External AI can be switched off
Each organization can switch external AI processing off. The Copilot then answers from the ledger only.
Notifications without amounts
Slack, Teams and webhook events carry names, references and statuses, never amounts.
Figures only within access
The CFO flash email and Copilot answers on Telegram carry figures, and only for the companies the recipient can see. A payment reminder tells a customer what that customer owes.
Not built yet, and labelled so
Each item below is on the roadmap and not available today. This page changes when one ships.
Hosting inside the Kingdom
Hosting in Saudi Arabia for groups whose data must stay in the Kingdom.
KMS-held keys in production
Support for encryption keys held in a managed key service is built. Switching it on in production is on the roadmap.
Independent certification
An independent assessment such as SOC 2 or ISO 27001. We will share its scope and timing once they are confirmed.
Third-party penetration test
An independent penetration test, with each finding tracked to resolution.
Naarvin holds no security certification today, and this site shows no badge it has not earned. If your security team has a questionnaire, we will answer it item by item.
Naarvin never moves money
Naarvin prepares and a person with the authority releases. That holds for payments, for postings and for access.