Agent scoping and access permissions

What’s Coming

We’re introducing a new scoping model for agents — the security boundary of the DPC — that allows them to be designated as:

• Public: Available to anyone with environment/project creation permissions or viewable as a list of agents.
• Restricted: Project: Usable only in a defined list of projects
• Restricted: Project + Environment: Usable only in specific project+environment pairs

Why It Matters

Agents serve as the runtime isolation mechanism in the DPC. Our customers have emphasized the need for robust separation of concerns — across teams, business units, and between production and non-production environments — during design time and administration to align with DataOps practices and meet regulatory obligations. Without this functionality, organizations rely on workarounds that are complex and hard to scale.

This update gives teams fine-grained control over which agents can be used where, improving security and clarity when configuring environments, schedules, secrets, and API-triggered pipelines and ensures that agent selection is intentional and aligns with organizational boundaries.

Who It’s For

Platform admins, enterprise teams, and organizations managing complex data operations seeking strong isolation in their data integration workflows