We're updating the issue view to help you get more done. 

Implement user-specific access control

Description

For some specific tasks it is critical to have user-specific access control, i.e. each user must have specific rights for the content he/she has created.

Environment

None

Activity

Show:
Vladimir Matskovsky
October 19, 2016, 9:00 AM

Yes, but it is not enough for our purposes. Let me explain the situation.
I'm working in the Museum of Paleontology, Moscow, Russia. For some reasons it is not possible for the Museum staff to put to the database information on all the items that come into Museum collection. Hence the collectors of the items do it themselves. Each collector put into database his part of the collection, but he shouldn't be able to edit other parts of the collection. As there are many collectors working simultaneously, ideally each of them must have "read+edit" access to the items he has created and limited (read only or closed) access to the items created by other collectors.

User known
October 19, 2016, 9:02 AM

You can use item-level access control which defaults to giving the author access to the items they create.

Vladimir Matskovsky
October 19, 2016, 9:18 AM

OK, thanks, I'll try this option. But isn't it a problem in this case to give rights for a Moderator to edit all these items?

User known
October 19, 2016, 9:20 AM

You'd have to do that on a per-item or per-collection basis. It could be a hassle... or not... depending upon your workflow.

Vladimir Matskovsky
October 19, 2016, 9:29 AM

OK, thanks. I'll try with per-item access level and then comment here again.

Assignee

User known

Reporter

Vladimir Matskovsky

Labels

Components

Affects versions

Priority

Major
Configure