Product / the shared workspace
A shared workspace between organisations,
without opening your information system.
RIGA is a shared workspace for organisations that have to handle a dossier with another organisation without opening their information system. Each party keeps its teams, its tools and its authority. RIGA records the documents, questions, answers and decisions exchanged between them.
Who it is for
- A lawyer or a firm handling a matter with a client or an opposing party.
- A CFO settling a disagreement with a supplier or a customer.
- Any organisation that negotiates, checks or signs with another.
In place today
- Hosting
- Documents hosted in France. Record and metadata hosted in the European Union.
- Verification
- Record exportable and verifiable offline, with no RIGA account.
- Your systems
- Each party keeps its system and its rights.
- AI assistants
- They act within a delegated technical scope; they neither sign nor consent.
01 / Today
To work with another organisation,
you open them a door, or you fall back on email.
You invite them into your portal or your extranet: they work in your system, by your rules, and your log is the one that counts. Or you go into theirs. Or everything goes by email, and six months later nobody knows who sent what, or when.
Your software does not leave your organisation.
Neither do your AI assistants.
02 / Connecting the software is not enough
A connection between two systems moves data. It does not say how two organisations work together.
Which version was sent? Who approved, refused or corrected it? Do both organisations hold the same record? A connection answers none of these questions.
At yours
Your processes, your teams, your AI assistants.
They run in your system, with your rights.
At theirs
Theirs, in theirs.
Neither organisation is there to host the other's work.
03 / The shared workspace
Each organisation keeps its system, its teams and its authority.
The dossier is opened between the organisations, outside their systems. Each party enters with its own rights: it sees only what is meant for it, its AI assistants act only within the technical scope delegated to them, and its system stays at home. Accesses, views, questions, answers, requests and decisions are recorded in a record each party can verify.
Your organisation
The other organisation
Two organisations handle the same dossier. Neither opens its system to the other.
04 / How it works
One dossier for two organisations,
in four steps.
01
You open the dossier and invite the other organisation
You create the dossier and invite the other organisation into it. You decide what their party sees and what it can file, download or request. Their system stays at home, and so does yours.
02
Each side works from its own system
Your assistant uploads documents, asks questions and answers within its permissions. It cannot sign, consent or legally bind the party.
03
Authorised people record the decisions
A decision is proposed in writing. The authorised people of each organisation read it and record it on behalf of their party, by simple signature, by signature on their device, or with a qualified certificate. An AI assistant can neither sign nor consent.
04
You close, and each party keeps the dossier
At closing, each entitled party receives the complete dossier — documents, decisions, record — and a report that lets it verify the dossier without us, at any time. At closing, the archive is sealed and the room key is disabled, then destroyed after thirty days. The encrypted archive remains available for the period set for the type of dossier — one year for a company sale, ninety days for an invoice dispute — and is never deleted before every entitled party has retrieved it.
05 / What a RIGA dossier holds
What you find there, in the order you use it.
Participants and a scope per party
Each organisation enters with its people, roles and rights, and sees only what is meant for its party.
Documents and document requests
Filed in the dossier or made accessible there, never sent. Requests are addressed to a party and tracked until filed.
Questions and answers
Each question is put to one organisation; the answer stays in the dossier.
Technical permissions, for people and assistants
You choose your assistant’s permitted actions within your own rights. It cannot sign, consent or legally bind the party.
Decisions recorded by authorised people
By simple signature, by device signature or with a qualified certificate. Reserved to people.
A record
Accesses, filings, questions, answers, requests, decisions and authorised assistant actions, in the order they happened.
Export and independent verification
Each party exports the record and verifies it on its own computer, with a public tool, with no account with us.
Closing with the dossier handed over
Each entitled party receives the complete dossier; the room key is disabled, then destroyed after thirty days.
06 / Three ways in
You use it as is, with your AI assistant, or from your own tools.
See the developers pageAs is
In the browser, nothing to install, for your teams and for the other organisation's.
With your AI assistant
Each organisation connects its own MCP-compatible assistant to read and contribute to the dossier within its granted permissions.
From your tools
By API, with signed notifications. The documentation is on the developers page.
A task can trigger work by your assistant.
A signed notification tells your system when a person assigns a work task. Your automation can then start your assistant, which reads authorised documents and submits its contribution to RIGA.
You configure this automation in your tools. RIGA controls access, sends notifications and records actions. Authorised people record decisions.
07 / Verification
The record verifies without us.
Each organisation exports the record and verifies it on its own computer, with the public tool of the VAL protocol, with no account with us. Verification covers the record: nothing was altered, every action was authorised, everyone stayed within their scope. It does not judge the substance of the dossier.
Security and protocol08 / Frequently asked
What we are asked before a dossier opens.
Does the other organisation have to install anything?
No. They receive an invitation and enter the dossier from their browser, with the rights you defined for their party. Nothing is opened in their information system, nor in yours.
What does the other organisation see?
What is meant for its party: the folders opened to it, the questions put to it, the documents requested from it. Nothing else. Every view is recorded.
Can our AI assistants work there?
Yes. Each organisation connects its MCP-compatible assistant and chooses its permitted actions. It cannot sign, consent or legally bind the party.
Can we integrate it with our tools?
Yes, by API, by MCP, by signed notifications or through Zapier. Your software can open dossiers, file documents, ask questions and receive events, with no dedicated screen.
What exactly is verified?
The exported record: that nothing was altered, that every action was authorised and that everyone stayed within their scope. Verification runs on your own computer, with the public, open tool of the VAL protocol (val-protocol.org), with no account with us. It says nothing about the substance of the dossier.
Where is the data hosted?
Documents are hosted with a French provider in France. The record and metadata are hosted in the European Union. Each room is encrypted with its own key. At closing, the archive is sealed and the room key is disabled, then destroyed after thirty days. The encrypted archive remains available for the period set for the type of dossier — one year for a company sale, ninety days for an invoice dispute — and is never deleted before every entitled party has retrieved it.
09 / To close
Two organisations handle the same dossier,
and neither goes into the other's systems.
Not at yours, not at theirs: a shared workspace, with a record each party can verify.
Neither host nor guest. RIGA.