Credentials and permissions

Credential and Principal are different

A credential authenticates a Principal; it is not the Principal itself. Studio displays the authenticated Principal in the Server/session context. Permission then controls which operations that Principal may perform.

One-time credential handoff

An issuance can return a one-time token. Save it through your approved secret process before closing the handoff, or use it for the current memory-only Studio session. Closing clears that local display and cannot show it again. It does not revoke the credential. Revocation is a separate, explicit permission-controlled operation.

Do not put credentials, bootstrap assertions or private keys in URLs, generic JSON, diagnostics, source control or public issue reports.

Query permission identity

Query execution is not inferred from the page label. It requires:

It also requires Read authority on every source Population at the exact Population identity. Authentication and Server readiness do not imply either permission.

Preview boundary

The Developer Preview is not licensed for Production Use and has not undergone an independent professional security review. Report security-sensitive findings privately through the confirmed contact; do not publish exploit details or sensitive evidence.