Project-scoped permission set assignments now require explicit project scope
UpdateVerifiedAdded Sep 22, 2026
Assigning a project-scoped permission set to a group or service token now requires all projects or a specific project. Requests without project scope return a 400 error.
Topics: Security
Summaries of vendors' own notes. Product names and logos belong to their owners; logos via logo.dev.
More dbt platform releases
Every dbt platform release| Date | Release | Type |
|---|---|---|
| Sep 2026 | dbt State generally available GA | GA |
| Sep 2026 | Lake Compute private beta: DuckDB-based engine for Iceberg tables Beta | Beta |
| Sep 2026 | Wizard Desktop native app in private beta Beta | Beta |
| Sep 2026 | ClickHouse connections for dbt v2.0 on the dbt platform in private beta Beta | Beta |
| Sep 2026 | dbt Charts public beta: YAML-defined dashboards on dbt models Beta | Beta |
| Sep 2026 | dbt State-powered state:* selectors for self-managed deployments in beta Beta | Beta |
| Sep 2026 | dbt State lag tolerance recommendations Update | Update |
| Sep 2026 | Analyst Read permission set available to all accounts Update | Update |
