Allow restricting the "Manage view" permission

Is your feature request related to a problem? Please describe.

Hi,

Currently, granting a user or group the "Manage view" permission for a single view also allows them to perform actions that affect the entire table and other views. For example, they can create or delete columns and rows and delete the view itself, even if the user or group does not have these permissions on the table or is a table manager.

It would be useful to separate view-specific editing from table-level management. A user should be able to modify an existing view (description, visible columns, filters, and sorting) without gaining additional permissions that affect the underlying table.

Best regards,

Mike

Describe the solution you'd like

One possible solution would be to restrict the scope of the "Manage view" permission so that it only applies to view settings. More like an "Edit view" permission without granting broader table management capabilities.

Describe alternatives you've considered

No response

Additional context

No response

Start by tracing how the "Manage view" permission is currently applied to view settings and table-wide actions. Define the permission boundary so users can edit descriptions, visible columns, filters, and sorting without creating or deleting rows, columns, or views. Done means the restricted permission no longer grants those table-level capabilities.