The idea behind permissions is simple enough: ‘permissions’ make up ‘roles’ that users are supposed to play as they are assigned those. Some roles enjoy more access rights than others, much the same as a project manager in life enjoys more access rights toward what constitutes a software project’s machinery, than a software developer, whose job is more often than not is confined to writing codes. Permissions, therefore, are a means to give a framework of access rights to a user according to his or her place on a project or, more broadly, in an environment of projects, such as in a research department, or a construction company.
Permissions are the central element of a role and are used as specific rights that a user has in relation either to the system as whole, or projects he or she is (or is not) part of. There is user-specific hierarchy of permissions. For example, a user with the role of Administrator (or, in short, Administrator) has the right (permission) to set permissions at will.
In Easy Projects, permissions are divided into three groups: 1) global permissions, 2) permissions in relation to a project(s) the user is a member of, and 3) permissions in relation to projects the user is NOT member of. See Roles, for more details. Also, you may want to look up the following topics: