Sensitive Resources

Sensitive resources are resources or actions that can expose credentials, affect production systems, mutate important records, change privileges, or impact external systems.

Reqflo can keep sensitive resources discoverable while restricting protected actions.

Common sensitive resources

Sensitive resources include:

• Secrets
• OAuth scopes
• Production credentials
• Production environments
• Destructive workflows
• Mutating production runs
• External integration configuration
• Billing
• SSO and SCIM
• User invites and role changes
• Permission delegation

Risk levels

Normal

A standard internal resource with no sensitive execution risk.

Examples:

• A staging-only request template.
• A read-only mock.
• A normal internal journey that uses non-production dependencies.

Sensitive

A resource that uses credentials, private data, privileged configuration, or restricted dependencies.

Examples:

• A secret-backed auth component.
• A journey that uses private customer data.
• An OAuth config with privileged scopes.

Production

A resource that targets production systems, production tenants, production credentials, or live customer-impacting systems.

Examples:

• A production environment.
• A production API credential.
• A journey that runs against live customer data.

Destructive

A resource that can delete data, mutate important records, trigger irreversible actions, change permissions, or affect external systems.

Examples:

• Refund workflow.
• Account cancellation workflow.
• Tenant deletion runbook.
• Permission-changing automation.

Sensitive does not always mean hidden

Sensitive resources can remain discoverable while protected actions are restricted.

Examples:

• A user can view that a production OAuth config exists without being able to use it.
• A user can view a journey without being able to run it in production.
• A user can use an approved component without being able to edit its scopes or secrets.

Restricted actions

Restricted actions commonly include:

• run against production or destructive targets.
• use of a restricted credential or component.
• attach of a secret-backed component.
• manage_scopes for OAuth or equivalent privileges.
• manage_secrets for secret-backed values.
• manage_access for sensitive resources.
• manage_integrations for external provider configuration.
• manage_sso and manage_scim.
• manage_billing.

Recommended practices

• Restrict risky actions, not normal discovery.
• Keep secrets and OAuth scopes tightly controlled.
• Separate production run access from staging run access.
• Review destructive and production access regularly.
• Give users clear denial messages when a dependency blocks an action.