#176 Area administrators

open
nobody
None
5
2016-06-14
2011-11-07
jonwitts
No

We use MRBS quite intensively at our school for all our IT labs, conference rooms and sports centre bookings. We would really like to be able to have an extra two levels of user rights. At present we have:
Site Administrator - can book all rooms, alter all bookings and create / delete rooms
User - can book all rooms and alter only their own bookings
* Viewer (non-user) - can only view bookings

What we would really like is this:
Site Administrator - can book all rooms, alter all bookings and create / delete rooms
Site User - can book all rooms and alter only their own bookings
Area Administrator - Can book all rooms in their area and alter all bookings in their area
Area User - Can book all rooms in their area and only alter their own bookings
* Viewer (non-user) - can only view bookings

I am not sure if this is a feature that others would like; but I imagine it would be useful for a lot of users of the system.

Thanks

Jon

Discussion

  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-11-09

    I've seen a few requests like this, but nothing seems to have happened on any of them. I would find it really useful to have area administrators, and areas that only certain users could book.

    I'm looking at implementing area admins at the moment, if anyone has any ideas or has already done work towards this please feel free to contact me!

    Ollie

     
  • Campbell Morrison

    Yes, I agree this is something that needs to be done and it must be up there near the top of the list. I like Jon's suggestion. It maybe also needs Room Administrators and Room Users, because I can see that some people may need them. We also need to decide whether the existing room and area admins need to be retained. If they are they certainly need to be renamed. I can see there might be a need to copy people for info whenever a room or area is booked. These would not be MRBS administrators but people who need to be notified so that they can prepare a room for a meeting.

    In the meantime it should be relatively easy to add something in yourself to implement area admins and area users. The function getWritable() in mrbs_auth.inc has a third parameter, $room, for precisely this purpose. getWritable() controls whether a user can book a particular room. The $room parameter is not used by standard MRBS, but I put it in with this in mind. You could then use the $user and $room parameters to check whether that user has permission for that room - perhaps against the users table if you are using 'db' authentication, or against a new table that you introduce or else against LDAP - though I'm not familiar enough with LDAP to know if that's possible.

    Similarly auth_book_admin(), which determines if a user is a booking admin, also takes a $room parameter. This too is ignored in standard MRBS, but could be used to implemet area admins.

    Hope that helps.

    Campbell

     
  • jonwitts

    jonwitts - 2011-11-09

    Hi Campbell,

    I will try to have a look at the code to see if I can see a way to get what we need and then share it back of course!

    I agree that a room user and admin would also be useful and I had thought of posting that in the original post; but thought it best to keep it simple!

    I fully agree that we need to retain (and rename) the existing room and area admins as we use these fields to enter (for example) our caretakers email addresses (who have no bookable access to the MRBS system), so the get notification emails for the areas and rooms they will be responsible for setting up.

    So to include the room admin and users in my list; it would look like this:

    • Site Administrator - can book all rooms, alter all bookings and create / delete rooms
    • Site User - can book all rooms and alter only their own bookings
    • Area Administrator - Can book all rooms in their area and alter all bookings in their area
    • Area User - Can book all rooms in their area and only alter their own bookings
    • Room Administrator - Can only book in their room, but can change any other peoples bookings in that room
    • Room User - Can only book in their room and can only edit their own bookings
    • Viewer (non-user) - can only view bookings

    I am wondering if this would be easier in the long run if we were to think about utilising the existing users table from db auth, and re-factoring the external auth methods to create a user in the local user table if they validate against the external auth system and do not exist in the local users table already... This would also probably lead the way to being able to set up multiple authentication methods in MRBS too...

    Jon

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-06-19

    I need the same features, particularly the area admin fetature.

    Thank's

     
  • Dave Orr

    Dave Orr - 2012-11-16

    I would also like to see an area admins feature.
    Don't like having my area admins in the current admin group.
    Too easy for a mistake to cause a whole room or area to disappear.

    Thanks

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2013-03-14

    Anyone has this implemented? Maybe i can help, since my company need this feature

     
  • TechGuy96

    TechGuy96 - 2014-09-24

    This feature seems like a great idea. I really wish it could be implemented as I am having to book many dates beyond our 6 week maximum for testing in labs throughout our school year. I've seen many, many request for this type of feature.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2015-09-09

    Any update on this feature? I too need the area admin feature.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2016-06-14

    One more that I would love these control features. It would be great and another idea would be permission by User area.
    Example:

    User 1 -> can only create reserves in the area (branch A)
    User 2 -> can only create reserves in the Area (Branch B)

    Thanks
    Tiago Butkcowsky

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks