• Help pages
• [Introduction]
• [Topic tree]
• [Annotating publications]
• [Publication lists]
• [Attachments]
  
• [Accounts]
• [Access rights]
• [Crossref]
• [Good practices]
• [Themes]
• [About]
  
• [See also the website for more documentation.]

Access rights on different levels

Aigaion users can be anonymous or not, can be assigned to different groups, and can be assigned different user rights. This makes it possible to restrict access to certain objects to a limited set of users. This restriction can apply to topics, publications, notes and attachments, and can be set separately for reading and for editing them.

What access levels are there?

For each of the above mentioned objects one can set a read_access_level and a edit_access_level. These levels can be:

• 'public' (object can be read or edited by everyone including anonymous users),
• 'intern' (object can be read or edited by all non-anonymous users),
• 'private' (object can be read or edited by the owner only)

What user rights are involved?

There are two types of user rights that also influence reading and editing access. The first are the normal read and edit rights. For example, a user who has no 'topic_edit' rights cannot edit a topic, even if all access levels of that topic are set to 'public'. The second are the 'override rights'. A user who has for example the right 'topic_read_all' can read every topic, even if he is not the owner and the access levels are set to 'private'.

Who can change the access level of an object?

The access levels can normally be changed only by the owner. However, users who have the appropriate override rights for editing (see above) can also change the access levels of an object.