Permissions: Implement permissions for all existing features, incl, create/edit/delete dv, datasets.

[eaquigley]

---

Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 4100, https://redmine.hmdc.harvard.edu/issues/4100
Original Date: 2014-06-16
Original Assignee: Gustavo Durand

---

We are at the point where we should be using permissions for existing functionality to make development more complete and ready and testing more comprehensive. Also, users will see how it will really work.

I think this is better done sooner than later so we don't have unexpected issues late in the schedule.

[scolapasta]

Current functionality should all be using permissions and commands. If you find anything not working, please open as a new (specific) ticket.

Now that there is a UI for roles and permissions will be easier to check.

[kcondon]

@scolapasta Can you give Elda and me another overview based on the current status? Thx

[kcondon]

Passing back until "all clear"

[scolapasta]

we should be able to test anything if the current required permissions. There are still some things that need to be cleaned up / tweaked related to assiging roles or what roles has what permission, but the core logic:

If you require perm A, and you have that permission via some role you have, then you should be able to perform the action. Otherwise, you should not.

[kcondon]

Basic permissions have been implemented with the exception of inheritance. There is some design work still happening but the primary functionality is there and issues will be opened as separate tickets.