search

magfest / ubersystem

MAGFest's Ubersystem - handles ticketing, staffing, analytics, volunteers, and tons more
http://magfest.org
GNU Affero General Public License v3.0
48 stars 55 forks source link

Separate shift creation/scheduling into its own permission #1473

Open nickthenewbie1 opened 9 years ago

nickthenewbie1 commented 9 years ago

We're starting to reach a point where we'd like to people to be able to create and assign shifts for people, but do not want to allow them to create new attendees/staffers.

bds002 commented 9 years ago

The specific section in Uber is called: Registration and Staffing under the Admin accounts. https://prime.uber.magfest.org/uber/accounts/

Registration DH's and Staff Ops DH's should be the only people that can go in and arbitrarily create/edit an attendee's contact data, badge status etc. Department heads should be able to see this data, but not edit it.

DH should be able to access the following sections of an Attendee's Data page:

Staffing : (yes or no)This attendee is volunteering (yes or no) Trusted ?

and: the "Assigned Depts" section

With the ability to leave Admin notes, or notes to review later.

The tabs for Shifts would fall under the Staffing (DH's access as well) The tab for History would also be viewable to review previous events and/or issues.

binary1230 commented 9 years ago

https://jira.magfest.net/browse/INC-161

thaeli commented 9 years ago

Like #1474 this is an upstream issue, please keep it in GitHub

On Oct 1, 2015, at 7:25 PM, Dominic Cerquetti notifications@github.com wrote:

https://jira.magfest.net/browse/INC-161

— Reply to this email directly or view it on GitHub.

binary1230 commented 9 years ago

yup, copy. see discussions on #1474 about magfest JIRA, and we'll be keeping this issue right here on github

bds002 commented 8 years ago

@dom this is related the granulation of permissions we where talking about in the office this past week

bds002 commented 8 years ago

Revisiting this issue since it affects the Research Team and MAGLabs. The RT wants to limit the numbers of staff in the system for MAGLabs, however each DH currently has to have access to the Registration/Staffing section of Uber:

capture

This should be broken up into two sections so that only Registration or Admin's can add entries to the Database. (Staffing would still be able to see the registration entries, mark and evaluate shifts, leave notes for review etc.....)

kitsuta commented 8 years ago

Unfortunately this change would require a pretty major overhaul of admin accounts and permissions.

The way we control people's access to pages is via the page rendering - either you can view X or Y page or you can't. There's no such thing as, for example, a "read-only" attendee details page. We MIGHT be able to separate staffing and registration, but someone with only staffing access would not be able to view the attendee's page.

On Tue, Jul 12, 2016, 13:35 Brent Smart notifications@github.com wrote:

Revisiting this issue since it affects the Research Team and MAGLabs. The RT wants to limit the numbers of staff in the system for MAGLabs, however each DH currently has to have access to the Registration/Staffing section of Uber:

[image: capture] https://cloud.githubusercontent.com/assets/8822346/16776870/4ecaa8a6-4835-11e6-9281-a1821c3d9fb8.PNG

This should be broken up into two sections so that only Registration or Admin's can add entries to the Database. (Staffing would still be able to see the registration entries, mark and evaluate shifts, leave notes for review etc.....)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/magfest/ubersystem/issues/1473#issuecomment-232120427, or mute the thread https://github.com/notifications/unsubscribe/AG3WBwkQw7fxHfjAAZf9tCDZ6fqphMT8ks5qU9BwgaJpZM4F4tg2 .