Allow groups to create blackouts and edit open/close times without create/copy rights.

4 votes

We have a couple “admin” groups we allowed to create and edit blackout dates and adjust open/close times on "their" spaces. With the recent changes, this is no longer possible without giving them the ability to add and copy spaces.

I'd like to request that a new permission (10.7) be added to Section 10.0 "Create, Edit and Copy Locations".
This new permission would allow the administrator to restrict the group's ability to create and copy locations.

Planned Blackout Management Location Management Suggested by: John Moore (16 Mar, '22) • Upvoted: 16 Oct, '23 • Comments: 3

Comments: 3

26 Sep, '22
Pamela Mason
Because Locations impact so many other function such as X25 reports & optimizer the creation and editing of a lot of the info on them need to be highly controlled. For example we cannot have people just updating the capacity, layout or features. In many cases for reporting purposes and also for people to find spaces that have what they expect it means we have to inactive the old room and create a new room. However, there is other information that they should be able to update but currently we have to have the System Admin do it.
23 Aug, '23
Pamela Mason
I think it would make more sense to allow people to create Blackouts based on.
1) Having Functional permissions to do so which should not be dependent on having any other permissions. This would essentially give them access to view/use the Blackouts Management Tool.
2) They would only be able to add or remove locations they had assign/unassign rights to.
Realistically these are the people that should be able to put a blackout on a location because they are the schedulers for the space. Blackouts are just another way of managing the schedule of a location. By having the Functional security control it allows us to restrict scheduler we do not trust to manage blackouts.
09 Jan
Pamela Mason
Also, Just because they have the functional permission to Edit and Copy Locations does not mean they can. They still have to have the Object level permissions to do this. So we really just need a separate permission for Creating Locations because the cannot be control by OLS but should be it's own permissions just like the permission to Delete Locations. FYI, it used to be separate and was change with the new Admin Utility,