Explanation
Organizations
How each customer's data stays separate from every other customer's, and what is still shared.
Each customer of Yaqeen is an organization, also called a tenant. Every person belongs to one organization. This page explains how the data is kept apart, what this means for your sandbox, and what is still shared.
What an organization owns#
Every request runs inside one organization. It sees only that organization's owners, stores, payouts, holds, cases, jobs, policy and audit lines. The review queue, approval limits, suppressions, rules, reserves, webhooks, API keys, usage and plan limits are also per organization.
The separation is built into the default database query for those tables, not left to each endpoint. A missing filter in the code returns nothing from another organization instead of leaking it. A request for another organization's record answers 404, the same as a record that does not exist.
Scoring and cases#
Scoring runs for one organization at a time, on its own data and with its own policy. Cases never merge across organizations, even when two organizations load the same bank account hash.
Your sandbox#
The sandbox is a second organization that belongs to you. It has its own data and its own yq_test_ keys. Nothing in it can reach your real organization, and a sandbox cannot have a sandbox of its own.
What is still shared#
- Detection. The same detection runs for every organization unless your agreement says otherwise. It reads only your organization's data when it scores your payouts.
- Payout and order ids. These are unique across all organizations today. Store, owner and buyer ids are unique per organization, so two customers can use the same store id.
- The audit chain. All organizations write to one hash chain. A customer reads only its own lines. See How the audit chain works.
Related#
- Set up your organization: the first steps for a new customer
- Sandbox: the safe copy for testing
- Roles: how people belong to an organization