Hey @der 

"I have full access on the cloned table, but only select rights on the source table."

When working with shallow clones in Unity Catalog on a dedicated or single-user cluster, Databricks enforces strict permission inheritance from the source table.

To perform any update/insert on a shallow cloned table, you must have:

• USE permission on the source catalog and schema

• SELECT permission on the source table

• MODIFY permission on the source table

Even if you’re modifying the cloned table, the underlying Delta metadata and lineage trace back to the original table, and Unity Catalog enforces this by default. Docs_dedicated

In standard mode works because it follows a different privileges system Docs_standard 

Hope this helps, 🙂

Isi