Managed Identity

Managed identity is the trust layer that decides who can read or mutate persona-aware state on behalf of a user.

What External Developers Need

If you are building a Level 2 layer around Prism and Mosaic, you still need a user-scoped identity model even if you are not exposing a full OAuth product on day one. Persona services should never be treated like anonymous stateless search.

• User auth should gate access to sentiments, onboarding, and window mutation
• Service auth is useful for backend workflows and operational tooling
• Scoped delegation becomes important if third parties will act on behalf of a user

How To Think About It

If this surface expands into a formal OAuth offering, its job is to let trusted third parties act against a user's taste state without leaking that state broadly. In other words: scoped, auditable delegation into Level 2 services.

Why This Page Is Light

This page stays light because identity architecture is mostly your application concern rather than a direct Prism or Mosaic feature. The important point is that Level 2 persona state needs explicit, auditable access control from the start.