Difference between revisions of "System-user role"
| Line 2: | Line 2: | ||
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. | ||
| + | |||
| + | |||
==Practices== | ==Practices== | ||
Revision as of 12:51, 3 April 2020
A system-user role (or, alternatively spelt, a system user role; also known as a permitted user role, user-access level or system-granted identity; a user role in WordPress; a user group in MediaWiki and HumHub; a security group in Odoo; an IAM role, where IAM stands for identity and access management, in AWS; an actor in the Unified Modeling Language (UML); 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.
