Architecture
The parts every CobraSphere product shares. Who a person is, which organisations they belong to, what their role lets them do, and which products they may open.
CobraSphere products share one identity service. It knows each person, the organisations they belong to and the role they hold in each one. The products read the same records, so a person signs in once and is the same person everywhere.
One person, several addresses, a role in each organisation, and the products they may open.
The parts
| Part | What it is | Read more |
|---|---|---|
| Person | One CobraSphere ID per person, with one or more verified email addresses | Identity |
| Organisation | A business in CobraSphere, joined through an access grant | Organisations |
| Role | What a person may do in one organisation, from Guest viewer to Owner | Roles |
| Domain claim | Proof with a DNS record that an organisation runs a domain | Domains and claims |
| Product access | Which CobraSphere products a person may open | Access |
| Invitations and requests | How people are invited, ask for access, leave or close an account | Invitations and requests |
| ZoneAudit data model | How ZoneAudit keeps scans, findings and access codes for a domain | ZoneAudit |
| Shared records | One id for each domain, person and organisation, used by every product | Shared records |
Two kinds of access
A role and product access answer different questions.
- A role says what a person may do inside one organisation. It belongs to the link between that person and that organisation.
- Product access says which CobraSphere products a person may open at all. It belongs to the person.
One sign-in
A person signs in with a one-time code sent to one of their email addresses. There is no password. Once signed in on a cobrasphere.com address, the person is signed in on the other CobraSphere sites under cobrasphere.com as well. Sites on other addresses, such as zoneaudit.com, receive the sign-in from the Account console without a second code.