IntegrAuth Academy
Identity, security and practical AI — free, from zero. Byte-sized lessons, real diagrams, hands-on labs, zero fluff. Two programs, each with its own exam and certificate.
English is hard? Your browser can translate this page into Tamil, Telugu, Kannada, Malayalam or Hindi. Tech words stay in English so you learn the real names.
How?
- Chrome on phone: ⋮ menu → Translate
- Chrome on computer: right-click → Translate to …
- Edge: the translate icon in the address bar
Personas & the identity fabric
One person can be a customer, an employee and a partner at the same time. Most systems cannot see that it is the same person. Fraud hides in that blind spot. Your goal: explain the golden rule, the identity fabric and the three ways to decide access.
- One person can have several personas.
- Golden rule: linked for risk, separated for access.
- An identity fabric connects your IdPs. It does not replace them.
- RBAC uses roles. ABAC uses context. ReBAC uses relationships.
The three-way collision
Priya works in Finance at a store chain. She also shops there, and she earns bonuses as a partner on weekends. One day she approves a ₹48,000 refund to her own customer account. Payroll sees an approval. The store sees a refund. The partner portal sees a bonus. Each system sees one normal thing. Nobody sees one person.
What is an identity fabric?
An identity fabric does not replace your IdPs. It connects them. Like threads in cloth, it joins the workforce IdP, the customer IdP, the PAM vault, HR and old application databases. Then it can answer: who is this identity, everywhere, right now, and what should we do? You get one view, one policy voice, one audit trail and one kill switch.
The full record of one person across all systems is the identity 360 view. The merged record at its center is the golden customer record: one clean profile that every system agrees on.
Three ways to build the fabric
Three ways to decide access
| Model | Gives access by… | Example |
|---|---|---|
| RBAC | Role | "Store managers may approve returns." |
| ABAC | Attributes and context | "…but only in their own store, during their shift." |
| ReBAC | Relationships | "Maya's mother may view the family plan, but not change it. She is guardian-of the account." This works well on a graph. |
Link the personas, and you can spot a fraud ring that no single system would see. Separate them, and a stolen customer login can never reach an employee's admin tools. The fabric does both.
Go deeper: where ReBAC comes from
Google's Zanzibar paper describes relationship-based access. OpenFGA is an open-source tool that implements it.
🧪 Interactive lab — enable JavaScript to play with this one.
Relationship-based access (ReBAC, or fine-grained authorization) is one of our core services. See what we build or talk to our team.