TimD - Ironically, that's how the system is supposed to work. Only owners (or folks they delegate) are supposed to add new scenarios that way. The "show all" created a bypass to that security and let effectively anyone add anything, which is concerning for obvious reasons.
We're having an internal debate now on the future of that functionality. While we recognize it provides a shortcut, that shortcut by it's nature can be used for malicious actions (not saying anyone has, but the option is there).
For now, the owner of the event (or individuals they have assigned as able to edit that event) will have to do the editing for scenarios not included when the event was created via the process I listed above. We'll let folks know when we come to a decision on the future of "view all".
I sort of figured that it was working as intended in that regard, I was just illustrating that (at least for some of us), the work-around isn't something we can use.While I can see the worry for abuse, the functionality of not having to generate multiple PFS #'s for different venues is a huge bonus.
As an example, the store I'm the liaison for has had at least 5 PFS #"s affiliated with it that I'm aware of, and some of those owners are either no longer involved in PFS or live out of state. I'm not sure what, if any, impact having multiple ID#'s for the same venue would have for internal database / reporting purposes for you folks at Paizo, but it's one reason I've been reluctant to just add several #'s for an ongoing venue.
I'm not trying to be critical of your processes, just trying to provide perspective from at least one user's point-of-view.
Thanks for the update!