I’m a level 4 area manager of Florida, and they just opened a new ramp on I-295 SB (and closed the old blanding ramp) so I need to add the ramp, and set it so users won’t miss the exit. I have User reports in the locations of the ramps, and I’ll update it to said reports. I can relock it when I’m done. (Similar thing I already did for I-295 NB)
Unlocked.
Updated. Added the future ramps off of Collins for I-295 S (to, and from). I didn’t name the one to get ONTO collins in case Waze wants to accidentally route you that way (just like I did on the Northbound ramp) but the ones that shouldn’t route you regardless cause there are better ways, I named, and locked them. It’s what they are projected to look like, and what I seen them to look like from the road. (almost finish building them). I locked the new ramp, and locked the interstate highway. Thank you for the quick unlock. I have all turns to and from collins as not allowed, and all the ramps turns (from I-295, and to Blanding) are allowed. so as soon as the update takes effect, it’ll be routing users correctly.
No problem. FYI, in this type of case I usually click the no-city and no-name boxes so the road isn’t red screaming for attention from another well meaning editor. 
I also usually set roads under construction as dirt roads because they stick out less in the editor and not at all in the client.
That is all just style differences, but functionally I’d make sure it wasn’t connected on at least one end just to make sure Waze doesn’t get creative and send people through the restricted turns.