Runtime & security

Technical reference for execution visibility and security-related runtime questions that do not belong in the everyday builder or operator path.

This section is a technical reference, not a second administration area.

For day-to-day configuration such as Connections, Members, Secrets, API Tokens and model-provider settings, use Control. For ownership, rollout and security review, use Administer and govern → Security and assurance.

Execution visibility

The customer-facing execution record lives in Monitoring. It is the place to inspect runs, traces, inputs, outputs and execution activity when debugging or reviewing operational behaviour.

A successful technical execution is not by itself proof that the business outcome was correct. Operational review still needs the relevant source data, configured rules and human decision boundaries.

Security reference

Security questions should be tied to the actual deployment: identities, Projects, Connections, credentials, data sources, external actions and the people who can change them.

Do not infer certification status, data-processing terms, retention commitments or other formal assurance facts from generic product documentation. Those require current assurance material supplied for the relevant review.