Decisions of record, under your organisation’s control
For the people who choose prorso for an organisation, and for the IT and security teams who assess it: how prorso fits your identity provider, your policies and your auditors, and, as plainly, what it does not have yet.
Your identity provider decides who gets in
People sign in the way your organisation already manages, follow the rules you set for them, and lose access when your directory says they have left.
Single sign-on, over OIDC or SAML
Your people sign in through your own identity provider: Okta, Microsoft Entra ID, Google Workspace, or any other that speaks OIDC or SAML. prorso connects the provider for you.
Require single sign-on
Require it of every account on your verified domains. Anyone there who signed in with a password or Google connects the provider once, and the other ways in are removed.
SCIM 2.0 provisioning
Your identity provider adds people and groups and removes them. Someone it deactivates loses the organisation, its groups and every role on its logs, the logs they owned go to a successor, and they are signed out.
Verified domains and managed accounts
Prove a domain with a DNS record, and the prorso accounts on it follow your session and two-step rules everywhere in prorso. Your admins can sign them out.
Require two-step verification
Members who sign in with a password add an authenticator app before they can open anything. A sign-in through your provider counts as the second step.
Session lifetimes
Shorten how long members stay signed in, down to one hour, and how long they may be idle, down to 15 minutes.
Groups
Share a log with a group as editor or viewer, and everyone in the group, now or later, has that role. Groups can come from your directory.
Who may be added
Limit membership to people at your own email domains. The people already outside the rule are listed for you.
Every administrative act is on the record
When someone asks who could see a decision, who changed a setting, or why a log still exists, the answer is already recorded, and you can hand it to whoever needs it.
An action log you can export
Everything administrative in your organisation is recorded. Your admins read and filter it, and export it as CSV or JSONL for your own tools.
A tamper-evident trail
Every audit event is hash-chained, and the chain is sealed and verified every night, so an alteration is detectable.
Auditor access
Give an outside auditor read-only access to chosen logs and their evidence until a date you set. It ends on its own, or earlier if you take it back.
Retention
Off by default. Or keep logs 1, 3, 5, 7 or 10 years after their last change. The first run only reports, and each owner has 30 days’ notice before a log is deleted.
Legal hold
Hold chosen logs, everything chosen people own, or the whole organisation. Nothing deletes a held log, not its owner and not retention, until the role that placed the hold lifts it.
Deliberate admin actions
Consequential actions by your admins need a sign-in from the last 10 minutes. Changing your sign-in, session, membership, AI or retention rules takes a written reason, kept with the change.
Your content, handled the way you would ask
What reaches AI, what is scanned, what is backed up, and where it all lives, stated rather than implied.
AI on your own key
Run prorso’s AI features on your organisation’s own OpenAI key, stored encrypted and never shown again. Without one, only the guide inside a log uses AI, on prorso’s own OpenAI account. Content is sent only when someone uses an AI feature, and is not used to train models.
Scanned attachments
Every upload is scanned for malware and checked against the type it claims to be. Nobody can open a file until it has passed.
Nightly backups
The database is exported every night to storage the application cannot reach, and each night’s run checks that the last one completed.
Export and erasure
Each person can download everything prorso holds about them. Requests to erase an account go to a register, and each is assessed and answered on the record.
Where your data is
Your logs, files and backups are stored in the European Union: the database in Google Cloud’s eur3 multi-region, files and backups in the EU multi-region, and server code in europe-west1 (Belgium). Text sent to an AI feature, the email we send and the abuse-prevention check (Google reCAPTCHA) are processed in the United States. Every third party that touches customer data is named, with 30 days’ notice before a new one.
What we do not have
- SOC 2 (None): No report, and none in progress.
- ISO 27001 (None): No certification.
- Penetration test (Not yet): Not yet conducted. The scope is written and ready for a vendor.
- EU / UK data residency (None): Not offered as a commitment. Data is stored in the EU, but there is no UK region and no choice of region, and AI requests and email are processed in the United States.
- Tested disaster recovery time (Not yet): Backups run and are verified. One restore drill has been run, on a small dataset, so no recovery-time figure is published.
- Single sign-on (Partial): prorso connects each organisation’s provider; it is not self-serve. Signing out at the provider does not end a prorso session already open.
- SCIM provisioning (Partial): Removing someone takes effect at the provider’s next sync, not instantly.
- API, webhooks and audit streaming (Planned): Not built yet; its scope waits on a customer’s named tools. The action log exports as CSV or JSONL meanwhile.
Questions IT teams ask
Can we require single sign-on for everyone?
For every account on your verified domains, yes. People from outside them, such as a partner you invite, sign in their own way, and your two-step and session rules still apply to them as your members.
What happens when someone leaves?
Deactivate them in your identity provider. At its next sync prorso removes them from your organisation and its groups, takes away their roles on logs, hands the logs they owned to a successor and signs them out. An admin can also remove them by hand, with a handover.
Does our content train AI models?
No. AI features call OpenAI’s API, whose commercial terms exclude API data from training, and only when someone uses one. OpenAI keeps a request for up to 30 days for abuse monitoring. With your organisation’s own key, requests go through your own OpenAI account; without one, the guide inside a log uses prorso’s.
Can we get our records out?
Your admins export the action log as CSV or JSONL, an evidence bundle comes with a manifest and an integrity hash, and each person can download everything prorso holds about them.
Can we keep logs for a dispute or an investigation?
Place a legal hold on the logs, on the people who own them, or on the whole organisation. While it is in force nothing deletes them, and only the role that placed it can lift it.