What Termina can access and how that access is used

Read-Only by Design

Termina operates with read-only access whenever possible.

This ensures:

• No changes to production

• No execution of actions

• No modification of pipelines or resources

Visibility is separated from control.

What Termina Can See

Depending on the system, Termina may access:

• Deployment metadata

• Service and environment state

• Configuration and infrastructure signals

• Timestamps and identifiers

Access is limited to what is necessary for visibility.

What Termina Cannot See

Termina does not access:

• Application source code

• Customer data

• Secrets or credentials

• Write or execute permissions

If data is not required for production awareness, it is not requested.

Why These Permissions Matter

Accurate production visibility depends on:

• Verified state

• Reliable timelines

• Cross-system correlation

Permissions enable Termina to explain what changed without guesswork.

Managing Access Over Time

Permissions can be:

• Reviewed

• Revoked

• Re-scoped

At any time through the provider’s access controls.