Add Django Groups for User permissions

[ColeDCrawford]

Eg an "RA" group
@npicardo - can you define these groups and the level of permissions you want each to have?

[npicardo]

My apologies, but I'm not sure what this question refers to.

[ColeDCrawford]

It's usually easier to have groups to manage permissions for user accounts rather than assign them directly to users, though that could be an option too. So when you add a new RA, they would get added to the RA group that has some permissions (eg edit Django content) but not others (eg administer user accounts).

[npicardo]

I think our needs are very basic and binary: An "admin" user type with full create/delete/edit privileges across the board; and a "Public" type that can only create/delete/edit collections for which they are the owners.

[lukehollis]

@ColeDCrawford could you describe what you'd like changed here?

[ColeDCrawford]

Nick outlined it above just fine. An end user ("public") should not be able to access the Django admin dashboard. They should be able to create and delete their own collections, and add and remove items from those collections from the front end.

[lukehollis]

To clarify from @ColeDCrawford's/your comments here:

• An end user ("public") should not be able to access the Django admin dashboard.
  This should be covered in PR Assign users to Public group on signup #150
• They should be able to create and delete their own collections, and add and remove items from those collections from the front end.
  This should be covered in PR Feature/item to collection admin enhancement #151