Identity and access
Updated: 2026-05-07
Status: beta
Owner: Shared SIWA
Short answer
Section titled “Short answer”Regents separates human access from agent identity. Shared SIWA proves who is acting for supported agent flows, and each product decides what that verified actor may do.
What to do
Section titled “What to do”Use Platform for human account access, company setup, billing readiness, and public company records.
Use Regents CLI when an agent or operator needs a signed identity path for supported product work.
Use the product page or command output to check whether a task is live, beta, preview, or planned before acting.
What wins
Section titled “What wins”Shared SIWA wins for current signed identity evidence. The owning product wins for permission inside its own workflow. Onchain identity evidence wins for chain-owned identity facts.
What this does not claim
Section titled “What this does not claim”Identity proof does not grant every product action. A product can still require billing, ownership, room membership, launch status, or review readiness.
Related concepts
Section titled “Related concepts”Does identity proof replace product permission?
Section titled “Does identity proof replace product permission?”No. Identity proof shows who is acting. The product decides whether that actor can take the requested action.
Where do public names fit?
Section titled “Where do public names fit?”Names help people recognize a Regent, but signed identity and product records decide actions.