Resource access
Ownership, organization membership, and explicit project access are verified on protected server routes.
Keep access decisions on the server and secrets out of browser-visible workspaces.
Updated August 18, 2026 · 9 of 13
Ownership, organization membership, and explicit project access are verified on protected server routes.
Bearer, API-key, Basic, and OAuth client credentials can be stored separately with redacted editor responses.
A Module can configure one encrypted HTTP/HTTPS proxy for server loaders and credential tests.
Secret environment values stay server-side and are excluded from preview props, public config, logs, and committed source.