Tips for testing ACL changes in growing GRIST projects?

Hi everyone!

We’re using the (awesome) GRIST tool for our community project.

We’ve set up some pretty complex ACL rules, since different types of users have different permissions depending on the tables.

The project has grown quite a bit, and we’re now at a point where we really need to make sure we don’t introduce regressions when changing the ACLs — like when adding or removing permissions for certain users.

Has anyone here figured out how to automate tests in GRIST to check that, after an ACL change, the right users can still access the right tables and edit the data they’re supposed to?

Would love to hear how others are handling this!

2 Likes

Interested in such good solutions!