Role-Based Access Control (RBAC) controls which areas of the SamurAI Portal a user can view and which actions they can perform.
Each SamurAI Portal user is assigned one role. The role determines the permissions available to that user, such as whether they can view security incidents, manage telemetry, create or update tickets, or administer users.
RBAC helps your organization apply the principle of least privilege by ensuring users have access only to the information and actions required for their responsibilities.
System and custom roles
The SamurAI Portal supports system roles and custom roles.
- System roles are predefined roles provided by NTT for common responsibilities.
- Custom roles are roles created by a Tenant Administrator with a selected set of permissions.
Use a system role when it meets the user’s responsibilities. Create a custom role when a different combination of permissions is required.
The Category column under Admin > Roles identifies whether a role is System or Custom.
Creating and saving a custom role does not assign it to a user. After saving the role, assign it to the relevant users through Admin > User Management.
Regional role availability
RBAC is available in the SamurAI Portal for tenants in Japan and Europe.
The system roles available to your tenant may vary by region. Refer to the applicable regional system-role catalogue below when choosing a role for a user.
Always review the permissions displayed under Admin > Roles before assigning a role. A similar role name or description does not guarantee identical permissions across regions.
Who can manage roles?
Users assigned the Tenant Administrator role can:
- View users in the tenant
- Invite new users
- Assign and change user roles
- View available roles, their associated permissions, and assigned users
- Create, edit, duplicate, and delete custom roles
- Delete users from the tenant
Users with other roles can access only the portal functions permitted by their assigned role.
For instructions on inviting users, assigning roles, and deleting users, see User Management.
Important information
Existing tenants
When RBAC is enabled for an existing SamurAI tenant, all existing portal users are initially assigned the Tenant Administrator role.
This approach ensures that existing users retain access during the rollout. Your organization must review its current user population and change each user to the most appropriate role as soon as possible.
NTT recommends reviewing user access with the individuals responsible for security operations, IT operations, service ownership, and access governance.
New tenants
For a new SamurAI tenant, the first registered portal user is assigned the Tenant Administrator role.
That user is responsible for inviting additional users and assigning appropriate roles.
Tenant Administrator coverage
Your organization should maintain at least two active Tenant Administrators wherever possible, providing a primary administrator and a backup.
This reduces the risk of losing administrative access when an administrator is unavailable, changes role, leaves the organization, or cannot access their account.
Keep the number of Tenant Administrators limited to those who need to manage the portal and user access. Assign additional administrators only where there is a clear administrative or coverage requirement.
View roles
To view the roles configured for your SamurAI tenant:
- Log in to the SamurAI Portal.
- From the main menu, select Admin > Roles.
- Select a role to view its permissions.
The Roles page displays the roles available to your tenant, a short description of each role, its category, and the number of permissions assigned.
The role details show the role’s name, description, category, and permissions.
Permissions are grouped by SamurAI Portal feature and, where applicable, by component:
- A check mark indicates that the role has the permission.
- A cross indicates that the role does not have the permission.
- A dash indicates that the action is not applicable to that component.
Use Search to find a feature or permission in the role details.
The Assigned users section lists the users assigned to the role. Review this list when checking access or planning changes to a custom role.
Permission actions
Depending on the feature and component, permissions can include:
- Read — View information or access a portal feature
- Create — Create new records or configurations
- Update — Modify existing records or configurations
- Delete — Delete records or configurations
- Upload — Upload files or evidence where supported
- Close — Close tickets or security incidents where supported
- Enroll — Enroll endpoints where supported
- Assign role — Assign a role to portal users
- Invite — Invite new users
An action applies to the feature and component against which it is listed. Permission to perform an action in one feature does not automatically grant the same action in another.
For example:
- Roles permissions relate to viewing and managing role definitions.
- User management permissions relate to viewing users, deleting users, assigning roles, and inviting users.
Creating a role and assigning a role are separate actions. Review both permission groups when assessing access-administration capabilities.
Grant permissions for user and role administration only where they are required for the user’s responsibilities.
Understand Core permissions
Core refers to the main information or functionality of a feature. The actions shown against Core apply to that feature’s primary records or functions.
For example, under General tickets, Core permissions control actions on the ticket itself, such as reading, creating, updating, or closing it.
Supporting components, such as attachments and communication channels, have their own permissions where listed.
Core is not an additional permission level and does not automatically grant access to every component within a feature.
Permissions used across portal views
Some permissions provide access to information used in several areas of the SamurAI Portal.
For example:
- Events permissions support views that use telemetry event data, including relevant dashboards and event graphs within integrations.
- Alerts permissions support views that display alert data, including relevant dashboards.
- Security Incidents permissions support incident views and dashboards that use incident data, including MDR metrics.
Dashboards are therefore not necessarily listed as separate features in the permissions table. Access to their information depends on permissions for the underlying data.
Permission to view an integration’s configuration does not, by itself, grant permission to view its event data. These are separate permissions.
System roles include the permissions configured for their intended responsibilities.
When creating a custom role, review the permissions for both the feature and the underlying information the user needs to access.
Validate the custom role against the user’s required workflows, including relevant dashboards, event views, attachments, and communication channels.
Federated View
Federated View provides consolidated Security Incident and General Ticket visibility across multiple tenants. It does not grant additional tenant access or override Role-Based Access Control (RBAC).
A user must have access to the relevant tenant and the permissions required to view the relevant information in that tenant.
Permissions continue to apply to both information and actions. For example:
- Security Incident permissions determine access to incident information and the underlying data used by incident dashboards.
- General Ticket permissions determine access to General Tickets.
- Permission to view an incident or ticket does not automatically grant permission to update or close it.
- Supporting information and functions, such as evidence, attachments, and communication, remain subject to their applicable permissions.
The information and actions available may therefore differ between tenants.
For more information, see Federated View.
Create a custom role
Use a custom role when the available system roles do not provide the combination of permissions required for a user’s responsibilities.
Before you begin, identify the features, information, and actions the role needs. Select only the permissions required.
- Log in to the SamurAI Portal as a Tenant Administrator.
- Select Admin > Roles.
- Select Create role.
- Enter a Name for the role.
- Enter a Description that explains the role’s intended responsibilities.
- Under Permissions, select the required actions for each feature and component.
- Review the selected permissions.
- Select Save.
A name and at least one permission are required to save a custom role.
Use a descriptive name, such as “Integration Support” or “Service Reporting”, rather than a person’s name.
Select permissions
Select an individual permission using the checkbox at the intersection of the component row and action column.
Use Search to locate the relevant features or permissions.
The page also provides feature-level and component-level selection checkboxes, together with a Select all visible option. Review the individual permission selections before saving, especially when using selection controls that affect multiple permissions.
For an explanation of permission actions, Core permissions, and access to information used across portal views, see the permission guidance above.
Assign the custom role
After saving the custom role, assign it to the relevant users:
- Select Admin > User Management.
- Locate the user.
- Open the user’s more options menu.
- Select Set role.
- Select the custom role.
- Select Save.
Each user is assigned one role. Selecting a custom role replaces the user’s previously assigned role; it does not add a second role.
For more information, see User Management.
Review a custom role
- Select Admin > Roles.
- Select the custom role.
- Review the role’s permissions.
- Review Assigned users to identify the users assigned to the role.
Review custom roles regularly and whenever the responsibilities of their assigned users change.
Edit a custom role
Before editing a custom role, review its Assigned users list and assess whether the revised permissions remain appropriate for those users.
- Select Admin > Roles.
- Select the custom role.
- Open the role’s more options menu.
- Select Edit.
- Update the role details or permissions.
- Review the changes and select Save.
Duplicate a role
Use Duplicate to create a new role based on an existing role’s permissions.
- Select Admin > Roles.
- Select the role you want to duplicate.
- Open the role’s more options menu.
- Select Duplicate.
- Enter a name and description for the new role.
- Review and adjust its permissions.
- Select Save.
Assign the new role to users through Admin > User Management.
Delete a custom role
Before deleting a custom role, review its Assigned users list and arrange any required role changes.
- Select Admin > Roles.
- Select the custom role.
- Open the role’s more options menu.
- Select Delete.
- Follow the instructions displayed in the portal.
Available system roles
The following descriptions summarise the intended use of the system roles. They are not exhaustive permission lists.
Custom roles are defined by your organization and are not included in these tables. Review Admin > Roles for the roles and permissions available to your tenant.
Japan
The following roles are available to tenants in Japan:
| Role | Intended users | Typical access |
|---|---|---|
| Tenant Administrator | Designated personnel responsible for portal and access administration | Broad access to supported SamurAI Portal capabilities, including user management and role assignment |
| Viewer | Users who require visibility of service information without making changes | Read-only access to permitted portal features and information |
| TAM | Technical Account Managers or users responsible for reviewing service information and coordinating activities | Access supporting service review, incidents, tickets, reporting, and operational coordination |
| Security | Security operations, security engineering, or incident-response users | Access supporting security monitoring, incidents, alerts, analysis, tickets, and permitted security administration activities |
| IT | IT operations, infrastructure, network, or telemetry owners | Access supporting telemetry, integrations, collectors, monitoring, related operational tickets, and permitted IT administration activities |
Europe
The following roles are available to tenants in Europe:
| Role | Intended users | Typical access |
|---|---|---|
| Tenant Administrator | Designated personnel responsible for portal and access administration | Broad access to supported SamurAI Portal capabilities, including user management and role assignment |
| Security Administrator | Users who require broad security operational and integration-management capabilities without administering user access | Access to incidents, tickets, alerts, and permitted telemetry/search, plus management of integrations and collectors; excludes user and role management |
| Security Analyst | Security operations or incident-response users who investigate and manage security findings | Access to security incidents and general tickets; read-only access to integration and collector configuration |
| IT Technician | System administrators responsible for setting up and troubleshooting data-source integrations | Management of integrations and collectors, permitted telemetry and diagnostic functions |
| Help Desk Analyst | Users who need to view and interact with tickets without accessing telemetry | Access to authorised tickets and their permitted workflow actions; excludes telemetry access and integration configuration |
| Viewer | Users who require visibility of service information without making changes | Read-only access to permitted portal features and information |
Choose an appropriate role
Start with a system role that matches the user’s responsibilities. If no system role provides an appropriate combination of permissions, create a custom role rather than assigning broader access solely to cover a limited requirement.
Japan
| User responsibility | Recommended role |
|---|---|
| Administers the SamurAI Portal, including user access and role assignment | Tenant Administrator |
| Reviews permitted portal information without making changes | Viewer |
| Coordinates service delivery, reviews service information, and works with NTT on customer activities | TAM |
| Investigates alerts and incidents, performs security analysis, or manages permitted security-related activities | Security |
| Maintains integrations, collectors, telemetry sources, and related IT operational activities | IT |
Europe
| User responsibility | Recommended role |
|---|---|
| Administers the SamurAI Portal, including user access and role assignment | Tenant Administrator |
| Performs security operational activities and manages integrations or collectors, without managing users or roles | Security Administrator |
| Investigates incidents, reviews alerts, and searches permitted security data without changing integrations or collectors | Security Analyst |
| Sets up and troubleshoots integrations and collectors, and manages related support tickets | IT Technician |
| Views and interacts with authorised tickets without requiring telemetry access | Help Desk Analyst |
| Reviews permitted portal information without making changes | Viewer |
Assign the lowest-privilege role that allows a user to perform their responsibilities.
For example, an engineer responsible for maintaining telemetry integrations should normally receive IT in Japan or IT Technician in Europe, rather than Tenant Administrator.
For tenants in Europe, a user who investigates incidents but does not need to change integrations should normally receive Security Analyst, rather than Security Administrator.
A user who only handles tickets and does not require telemetry access should receive Help Desk Analyst in Europe.
A stakeholder who only needs to review permitted service information should normally receive Viewer in Japan or Europe.
Review access before assigning roles
Before assigning or changing a user’s role, review:
- The user’s current responsibilities
- The roles available to the tenant and the services the user needs to access
- Whether the user needs to manage users or assign roles
- Whether the user needs to configure integrations or collectors
- Whether the user needs telemetry search, troubleshooting information, or only ticket access
- Whether the user needs access to security incidents, alerts, reports, or evidence
- Whether the user needs to create, update, close, or delete records
- Whether the user needs to export information or perform response actions
- Whether the user still requires SamurAI Portal access
- Your organization’s internal access-control and approval requirements
Review role assignments regularly and when a user changes responsibilities, changes team, stops supporting a service, or leaves your organization.
Next steps
- To view, invite, and manage users, see User Management.
- To understand the capabilities available in the SamurAI Portal, see SamurAI Portal User Guide.
- To request assistance, raise a request with the SamurAI SOC through the SamurAI Portal.