Hi @boitumelodikoko ,

Weird, it looks like a bug. MODIFY is a valid permission for table object. You can check it yourself in docs:

Unity Catalog privileges and securable objects | Databricks on AWS

Modify allows user to add, update, and delete data to or from the table if the user also has SELECT on the table as well as USE CATALOG on its parent catalog and USE SCHEMA on its parent schema. Since privileges are inherited, you can grant a user the MODIFY privilege on a catalog or schema, which automatically grants the user the MODIFY privilege on all current and future tables in the catalog or schema.

So, unless your table is foreign table it should work. In my opinion you can raise a bug on databricks support. As a workaround for now, you can request ALL PRIVELAGES permission.