Easier Bulk Permissions Updates (and/or Defaults)

Feature Requests
1

image
image1486×328 15.3 KB

I would love to be able to set a default option for Role > Table, where for example “Read is ON by default”. This will help when new fields are being added - I don’t have to go into each permissions config and tick the new fields.

Conversely, I may also set “Create/Update default = OFF” so ensure that most new fields in this table aren’t editable by this Role.

The in-between request here would be to allow me to “set all to ON/OFF” for read/update/create to save me for clicking Read on 25 new fields.

All quality of life stuff :slight_smile:

2

In fact… Update/Create does have a default at the top? Or is that a bulk-change?

3

Thanks for the suggestion and feedback @Russ !!

I can definitely see why this would be useful.

Just to clear things up, the switches for create and update aren’t for defaults.

If you toggle it off, those roles won’t be able to create or update any records in that table, so appropriate forms won’t be available.

A default though would make sense

1 Like
4

Default would honestly replace 90% of the permissions config we do, because we almost always need a more nuanced per-field or per-button approach in the App anyway.

For example, in some sections some users can make some changes based on the data on the record. That’s not managed in the Data layer.

eg “if this Licence record is not yet Status=Verified, the User who owns it OR two admin roles are able to Edit fields 3, 4 and 5., but when Status=Verified, only Admins can Edit field 5.”

But this is just how we tend to build! :slight_smile:

1 Like
5

Great insight - thanks @Russ