Environment level permissioning


Have another use-case where environment level permisioning is required. Is there any update on when this will be released?



1 Like

would be nice for QA testers who don't/shouldn't have access to prod data

You can do this if you put the users in a group and then once they have loaded the app can load the _environment parameter in the URL.... using urlparams, etc...

You can also, based on user roles, bake into the queries that if user is in role X and environment is "production" then disable query

Thanks Scott, however this doesn't suffice for us in terms of security concerns. We really are looking for a separation between edit access and viewer access, and environmental access more generally.

Got it - separation of church and state!

1 Like

Hey there! This is something that's currently in progress, the dev team is targeting the end of Q4 2022 as a release date :slightly_smiling_face:

1 Like

Hey folks,

I have some unfortunate news - this was slated to be released at the end of last year but the project is now on hold :pensive: Our devs had been working on this feature for some time, however the team responsible for it needed to consolidate their efforts to work towards a separate feature.

This is a widely requested feature and so it is definitely still on the radar, however, we no longer have a timeline for its release.

Sincere apologies for this miscommunication. We'll try and continue to keep this thread up to date with any changes and, as always, let us know if you have any questions or concerns.