Role Console Guide

This page provides a complete guide to using the Role section of the Namirasoft Access Console. It explains how to create, manage, and assign Roles, which are collections of Policies grouped together to simplify user access management. Roles allow administrators to assign multiple permissions efficiently while ensuring consistent access control across the Namirasoft ecosystem.

What Is a Role?

A Role is a named grouping of one or more Policies that defines a user’s overall access within the Namirasoft ecosystem. This grouping allows administrators to quickly assign complex access rules without configuring each Permission or Policy individually.

 

Roles act as templates for access management. By assigning a Role to a user, you automatically grant all the Policies linked to that Role. This approach ensures that access is applied consistently and efficiently across multiple users or applications.

Why Roles Matter

Roles matter because they provide an organized, scalable way to manage access. Instead of assigning individual Policies to each user, a Role lets you bundle Policies into meaningful access levels.

 

This design improves security, reduces administrative overhead, and ensures that access rules remain consistent across users and applications. Roles also help enforce organizational standards and make it easier to audit user access.

How Namirasoft Access Uses Roles

Namirasoft Access applies Roles by linking them to Policies. When a Role is assigned to a user, the system automatically grants all Permissions contained in the associated Policies.

 

Roles can include multiple Policies, each of which may apply to different products, entities, or actions. This layered approach allows for precise, flexible, and reusable access control.

Overview of Roles Fields and Options

This section explains each field and item visible when creating or managing a Role in the console:

 

• ID (String): A unique identifier automatically assigned when the Role is created. It is used internally to reference the item in the system.

• User ID (Namirasoft Account’s ID): This is the unique ID of the Namirasoft Account that created the Role. It links the Role to a specific user for access control and tracking but does not affect its function.

• Name (String): This is the unique name assigned to the Role. The name should clearly convey the access level or purpose of the Role.

• Description (String): This is an optional field where you can provide a human-readable explanation of the Role. A clear description helps administrators and users understand the scope and purpose of the Role.

• Policies (Enum): This links the Role to one or more Policies. Each Policy included in the Role defines specific Permissions, allowing the Role to provide a comprehensive set of access rules. A Role can contain multiple Policies, enabling broad or granular access as required.

• Created At (DateTime): This timestamp indicates when the Role was originally created.

• Updated At (DateTime): This timestamp indicates the last time the Role was modified.