URs closure by editors Lev. 1

We have found that some L1 editors can manage and close any URs in the areas they drive.

Our latest update was that L1 editors could ONLY close the URs they created … But we found some editors Lev. 1 (users from before 2017) who can close ANY UR (even not created by themselves) in the areas where they have driven.

I have already sent some examples to my CM in the past to analyze the problem.

This is the last one that has been reported to us.

Hi Maria,

Thank you for reporting this issue. I have added this case to the internal ticket and the team will review it.

Could you please add more examples if you notice fresh ones?

Regards,
Nataliia

Hi Maria,

Could you please tell if you noticed any new similar reports?

Thank you in advance,
Nataliia

An editor informed me that these URs in Germany could be closed by an L1 editor

https://www.waze.com/de/editor?zoom=5&lat=49.463202&lon=7.453249&mapUpdateRequest=18933478&env=row
https://www.waze.com/de/editor?zoom=5&lat=49.459081&lon=7.457378&mapUpdateRequest=18933477&env=row
https://www.waze.com/de/editor?zoom=5&lat=49.458163&lon=7.806063&mapUpdateRequest=18924648&env=row

This is a UR that I sent via the reporting tool and that could be closed by an L1 editor

https://waze.com/de/editor?env=row&lat=48.90972&lon=9.10747&marker=true&zoomLevel=18&mapUpdateRequest=18952817

Regards, Stefan

Is it possible that the L1 editor has an unknown/hidden AM? I think that overrides some of the rules.

That’s right, they’re both area managers. I’ll try to check this problem with an L1 editor who is not an area manager.

Hi @miole67 ,

We have been waiting for a response on this bug for a while. Since it’s been a long while, we will automatically close this report for now.

We apologize if this has caused any inconvenience or if this is a misunderstanding from our side. If this issue is still occurring please submit a new bug with all the relevant information and we’ll make sure to fully revisit it again.

Thank you and have a great day!