The relationship between users and roles in databases can be seen from the fact that roles seek to provide some form of template that would help in the assignment of permissions to the individual database users. The relationship reflects more on the fact that each user must be assigned a specified role while manipulating a database, especially in ensuring that the information in the database is not damaged or stolen. User functions may differ depending on the expectations of the user with regard to handling the database with some users have both read and write privileges, others having the read or write only privileges. That serves as a clear indication of the fact that roles seek to play a critical role towards defining the extent to which a user would be able to manipulate a database.
On the other hand, it can also be argued that the relationship reflects more on the fact that users are assigned roles, which seek to define the permissions that they would have when manipulating the database. When assigning permissions, the administrators do not assign permissions to users but assign them to roles. That means that if a user is assigned a given task, he or she would have a clear guideline of what he or she is expected to do as part of the manipulation process of the database. Users may have varied roles depending on the assignment by the database administrators. That serves as a clear aspect that seeks to highlight the existing relationship between users and roles while considering their usability as part of the manipulation of a database.
Delegate your assignment to our experts and they will do the rest.
The main reason why administrators use roles rather than merely assigning rights and privileges to each user is to help in maintaining data security, especially when dealing with highly confidential data. One of the key challenges that companies and organizations are facing revolves around the issue of data security, as it becomes essential for them to consider all aspects of advancing overall security. By assigning rights and privileges to an individual user, the companies seek to expose themselves to high possibilities of infiltration, as a third party may seek to use the user’s credentials to access private data. Consequently, this creates the need for having to use roles, which seek to create limitations in terms of what the users would be able to do concerning their manipulation of the database. The outcome is that this serves as a guarantee that the database administrators would be in a favorable position that would allow for limitation of access to private data.
When dealing with new hires, the primary expectation for the administrator is that they would be given minimal roles, which, in most cases, is read-only in a bid to ensuring that they are not able to manipulate the data in a manner that adversely affect the company. However, as the hires rise in their positions within the company, they would be accorded extra roles, which may include writing privileges, meaning that they would be able to change the data within the database. In the case of job changes, one of the critical expectations is that administrators would be expected to revoke all user credentials from an employee that is leaving the firm or company. That seeks to ensure that the former employees would not access data that they would use in other companies or manipulate the data negatively.
