Editor role required to set the "current" environment variables

Hello,

One of my team mates with “Read-only” project access reported that he could not change the “Current Value” column for any environment variable - he could edit the value, but the “Save” button was inactive for him (both in Web App and Desktop one) - i’m attaching a screenshot I got from him.

My (and his) intuition is that those values are strictly private (as they’re supposed to be stored locally), not related to project, so they should not require user to have “Editor” role. Anyways, that made our Apidog project practically unusable for him.

In this case I had no problem to bump his permissions up (which resolved his issue), but it looks to me as a pretty serious bug.

Thanks for the feedback,I will report this situation to the product manager.

Hi,
Any update on this? The issue still occurs.

About 50% of my team members have “Editor” role just to be able to use Apidog for making requests >.<.
One of them by mistake removed core Common Parameter and I almost got a heart attack because I was afraid that It would also remove its value for ~200 endpoints that we have.

Apologize for any inconvenience caused, we will expedite the optimization process.

Hi,
I see that you fixed this - thank you :slightly_smiling_face:

However, there’s another, similar issue: Apidog requires user to have “Editor” role to in order to create any environment (even if the user intention is to create a “Private” environment)

Yes, because the environment is the content of the project, the editor role is also required to create or modify the environment