Difference between revisions of "System-user role"
(→Related coursework) |
|||
| Line 3: | Line 3: | ||
The ''Role'' is an identity that a system assigns to a particular user with permission policies that determine what the identity can and cannot do in the system. However, the ''Role'' does not have any credentials (password or access keys) associated with it. Instead of being uniquely associated with one person, a role is intended to be assumable by anyone at a specific level of permissions. | The ''Role'' is an identity that a system assigns to a particular user with permission policies that determine what the identity can and cannot do in the system. However, the ''Role'' does not have any credentials (password or access keys) associated with it. Instead of being uniquely associated with one person, a role is intended to be assumable by anyone at a specific level of permissions. | ||
| − | ==Related | + | ==Related lectures== |
*[[Effort Engineering Quarter]]. | *[[Effort Engineering Quarter]]. | ||
[[Category: Septem Artes Administrativi]][[Category: Articles]] | [[Category: Septem Artes Administrativi]][[Category: Articles]] | ||
Revision as of 12:56, 4 January 2019
A system-user role (or, alternatively spelt, system user role; also known as permitted user role, user-access level or system-granted identity; user role in WordPress; user group in MediaWiki; IAM role, where IAM stands for identification and access management, in AWS; hereinafter, the Role) is a set of capacities often called permissions that a system grants to any user who belongs to a particular Role.
The Role is an identity that a system assigns to a particular user with permission policies that determine what the identity can and cannot do in the system. However, the Role does not have any credentials (password or access keys) associated with it. Instead of being uniquely associated with one person, a role is intended to be assumable by anyone at a specific level of permissions.
