What causes dbt Group / Access Restriction Error?

A model is declared `access: private` and a model in a different group tries to `ref()` it. A cross-project `ref()` (dbt Mesh) targets a model declared `access: protected` in the upstream project. The model group was restructured and a previously accessible model is now in a group with stricter access. A package upgrade changed a model's access level to `private`, breaking existing `ref()` calls

How do I fix dbt Group / Access Restriction Error?

Check the model's access level: look for `access: private` or `access: protected` in the model's YAML config.. If access needs to be shared across groups, change the access level to `public`: `config: access: public`.. If the access restriction is intentional, move the consuming model into the same group as the source model.. For dbt Mesh (cross-project refs), the upstream model must be declared `access: public` and published via a dbt Cloud project connection.

Medium severitydbt

Power BI Refresh Error:
dbt Group / Access Restriction Error

What does this error mean?

A dbt model attempted to ref() a model whose access level is set to private or protected and is not accessible from the current project or group. Introduced in dbt 1.5, model groups and access levels enforce project-level API boundaries.

Common causes

1A model is declared `access: private` and a model in a different group tries to `ref()` it
2A cross-project `ref()` (dbt Mesh) targets a model declared `access: protected` in the upstream project
3The model group was restructured and a previously accessible model is now in a group with stricter access
4A package upgrade changed a model's access level to `private`, breaking existing `ref()` calls

How to fix it

1Check the model's access level: look for `access: private` or `access: protected` in the model's YAML config.
2If access needs to be shared across groups, change the access level to `public`: `config: access: public`.
3If the access restriction is intentional, move the consuming model into the same group as the source model.
4For dbt Mesh (cross-project refs), the upstream model must be declared `access: public` and published via a dbt Cloud project connection.

Frequently asked questions

What is the difference between private, protected, and public access in dbt?

`private` means only models in the same group can ref it. `protected` (default) means models in the same project can ref it but cross-project refs are blocked. `public` allows cross-project refs in dbt Mesh.