Roles + Permissions UI

[eaquigley]

---

Author Name: Michael Bar-Sinai (@michbarsinai)
Original Redmine Issue: 3497, https://redmine.hmdc.harvard.edu/issues/3497
Original Date: 2014-02-03
Original Assignee: Mike Heppler

---

See mockups at the parent ticket, #3432.

[eaquigley]

---

Original Redmine Comment
Author Name: Michael Bar-Sinai (@michbarsinai)
Original Date: 2014-02-14T15:55:17Z

---

functional implementation done. Not at all pretty.
The actual design differs from the proposed one - I added a "Dataverse" tab to allow place for the guest roles widgets.

[mheppler]

Once upon a time we thought Roles + Permissions would live in a popup, with tabs, but upon development, some of that was changed. We should decide how we want this to eventually look and function, and then implement it, so we can close this ticket.

[pdurbin]

I like the mockup in this ticket. The permission engine flexibility can be simplified in the GUI.

This ticket has been closed but it sounds like #602 is the place where the GUI will be figured out.

[mheppler]

Mockups that will be testing in usability sessions this week: https://iqssharvard.mybalsamiq.com/projects/permissionspartii-dataverse40/grid

[mheppler]

There looks to be a duplicate "Roles + Permissions - UI Improvements" issue #602 that outlines a few notes that I will include here, then mark it as a duplicate before closing.

---

Author Name: Mike Heppler (@mheppler)
Original Redmine Issue: 4033, https://redmine.hmdc.harvard.edu/issues/4033
Original Date: 2014-05-27
Original Assignee: Mike Heppler

---

After meeting with Liz and Michael, we've outlined some improvements to the workflow and UI.

• Better express what Inherit Assignments means
• Create predefined roles that cannot be deleted (i.e.-data curator)to provide users with roles when they don't feel the need to create ones specifically for their dataverses
• Condense the workflow into a simpler, easier to understand view.
• Create popup for the workflow, rather than a separate page.
• Rather than tabs, try expand/collapse panels.
• Make Users table the initial view.
• Take into consideration how Invite Users/Create Groups will work into the workflow.

[mheppler]

Linking related "Permissions" #25 which relates to the backend work.

[mheppler]

Sent to @scolapasta to develop based on the mockups [https://iqssharvard.mybalsamiq.com/projects/permissionspartii-dataverse40/grid].

[scolapasta]

This is one of those long standing, umbrella type issues. I am sending to QA, as we have now delivered a roles and permissions UI. Individual tickets have and should continued to be opened separately.

[kcondon]

Delivered, additional tickets being opened,closing.