This is the multi-page printable view of this section. Click here to print.
Admin
1 - User Management
To view the users in your SamurAI tenant, select Admin > User Management from the main menu.
The user list displays information including each user’s name, username, assigned role, account status, creation date, and last login.
Tenant Administrators can invite users, assign and change roles, and delete users from the tenant.
Invite users
Invite users through the SamurAI Portal.
Review the role’s permissions before inviting users. If a custom role is required, create and save it under Admin > Roles before assigning it.
- Log in to the SamurAI Portal as a Tenant Administrator.
- Select Admin > User Management.
- Select Invite users.
- Select the system role or custom role to assign.
- Enter the user’s email address. To invite additional users with the same role, select + Add another person and enter their email addresses.
- Complete the invitation using the controls displayed in the portal.
Each invited user receives an email from no-reply@security.ntt with instructions to register their account and complete their account details.
For registration instructions, see Getting Started with SamurAI MDR.
View a user’s role
Select Admin > User Management and locate the user.
The Role column displays the user’s assigned role.
Each user is assigned one role. The role determines which portal features and information the user can access and which actions they can perform.
For information about system roles, custom roles, and their permissions, see User Roles.
Change a user’s role
- Log in to the SamurAI Portal as a Tenant Administrator.
- Select Admin > User Management.
- Locate the user.
- Open the user’s more options menu.
- Select Set role.
- Select the required system role or custom role.
- Select Save.
The selected role replaces the user’s previously assigned role; it does not add a second role.
Access for users who work across multiple tenants
When reviewing access for a user who works across multiple tenants, confirm which tenants they need to access and which information and actions they require in each tenant.
Federated View does not grant additional access. Ensure that the user has the appropriate access and permissions for Security Incidents, General Tickets, or both in each relevant tenant.
Assign access according to the user’s responsibilities and the principle of least privilege. A need for consolidated visibility does not, by itself, require the Tenant Administrator role.
For more information, see User Roles and Federated View.
Delete users
Delete users who no longer require access to your SamurAI tenant.
Before deleting a user:
- Confirm that you have selected the correct username.
- Check whether the user is a Tenant Administrator.
- Ensure that your organization retains appropriate Tenant Administrator coverage.
To delete a user:
- Log in to the SamurAI Portal as a Tenant Administrator.
- Select Admin > User Management.
- Locate the user and verify their username.
- Open the user’s more options menu.
- Select Delete.
- Follow the instructions displayed in the portal to complete the deletion.
Use Set role instead of Delete when a user still requires portal access but needs different permissions.
NTT recommends maintaining at least two active Tenant Administrators wherever possible, providing a primary administrator and a backup.
User status
The Account Status column shows the user’s registration status.
| Status | Description |
|---|---|
| Invited | The user has been invited but has not completed account registration. |
| Active | The user has completed registration and their account is active. |
Review user access
Review the user list regularly and whenever a user changes responsibilities or leaves your organization.
- Assign the lowest-privilege role that supports each user’s responsibilities.
- Review custom-role permissions as well as individual role assignments.
- Keep Tenant Administrator access limited to users with an administrative or coverage requirement.
- Delete users who no longer require access to the tenant.
For information about reviewing role permissions and assigned users, see User Roles.
2 - User Roles and Access Control
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.
3 - User Settings
Select your user account at the top right of the SamurAI Portal to access your settings.

Figure 1: User Settings
Notification Settings
You can manage notifications you receive from the SamurAI Platform by adjusting your personal notification settings. These settings apply only to your account and do not affect other users.
Role-based availability
The notification categories available to you depend on your assigned role, the features enabled for your SamurAI tenant, and the resources you are permitted to access. Your assigned role is displayed in the user settings menu.
Notification settings do not grant additional access. You can configure notifications only for portal features and resources that are available to your account.
If your role does not permit access to a feature or resource, its notification category is not displayed in your notification settings.
If you require access to an unavailable feature or notification category, contact a Tenant Administrator for your SamurAI tenant.
To ensure your notification preferences work correctly, notifications must remain enabled for each individual Collector, Integration, and Network Traffic Analyzer. For details, see the relevant sections:
Notification Behavior by Category
The notification categories displayed in the portal depend on your assigned role and tenant access. Categories are available only where you can access the related portal feature and resource.
- Collectors, Integrations and Network Traffic Analyzers: Notifications are triggered by status changes (e.g OK, Warning, Critical, Pending, Unknown)
- Security Incidents and General Tickets: Notifications are triggered by actions (e.g created, updated, closed, comment added)
Default Notification Settings
When your account is created, SamurAI applies default notification preferences only for notification categories that are available to your role and tenant.
If a notification category is not available to your role, it is not displayed in your notification settings and no default preference is applied for that category.
| Notification Category | Default Setting |
|---|---|
| Collector | Critical Status |
| Integration | Critical Status |
| Network Traffic Analyzer | Critical Status |
| Security Incidents | Created, updated, closed, comment added |
| General Tickets | Created, updated, closed, comment added |
How to Update Your Notification Settings
- Open the SamurAI Portal and select your user profile in the top right corner
- Click Notification Settings
- Choose a notification category and use the dropdown menu to select the state or action for which you want to receive notifications
- Click Save. If you have access to multiple tenants you can Save on all tenants
Appearance
Choose between a light or dark appearance for the application by toggling between the two modes.
Language
Toggle between the supported languages - English, Swedish or Japanese.
Time Zone
By default, the portal uses your browser’s time zone (detected from your device’s operating system) for timestamps displayed. You can override this by selecting a different time zone in your profile settings.
Tenant
Tenants that you belong to are listed. If you have multiple tenants simply select the tenant you wish to view.
To review Security Incidents and General Tickets across multiple tenants without switching between tenant lists, see Federated View.
Federated View
Federated View allows you to review Security Incidents and General Tickets across the tenants you are authorised to access, without switching between individual tenant lists.
It is intended for users who oversee multiple tenants, such as a central security team supporting several business units or organisations.
Enable Federated View
- Select your user account in the top-right corner of the SamurAI Portal.
- Turn on Federated View.
The Portal displays a Federated indicator to identify the active view.
You can then select:
- Security Incidents - review Security Incidents across your authorised tenants.
- General Tickets - review General Tickets across your authorised tenants.
- Dashboard > Security Incidents - review current open Security Incidents, with a breakdown by tenant.
The Security Incidents and General Tickets lists include a Tenant column identifying the tenant associated with each record.
Access and permissions
Federated View does not grant additional access or change your role and permissions.
The information you can view depends on both your access to each tenant and your permissions for the relevant information in that tenant. Your permissions also determine which actions you can perform.
For example, permission to view General Tickets does not automatically grant permission to view Security Incidents. Similarly, permission to view an incident or ticket does not automatically grant permission to update or close it.
The Security Incidents dashboard is subject to your permissions for the underlying incident data.
For more information, see User Roles.
Return to an individual tenant
- Select your user account in the top-right corner.
- Turn off Federated View.
- Use the Tenant selector to select the tenant you want to view.
Federated View provides consolidated incident and ticket visibility. Return to an individual tenant to use other tenant-specific Portal features.
Missing information
If an expected tenant, incident, or ticket is not visible:
- Check that Federated View is enabled.
- Check any active list filters.
- Ask a Tenant Administrator to confirm your access and permissions for the relevant tenant.
News Feed
The news feed is populated by the SamurAI Security Operation Center (SOC) analysts and may include:
- any issues or maintenance affecting service
- news such as how we are handling new and emerging threats
- links to blog posts on interesting security research
- updates on new releases
The news feed is viewed by clicking on the news icon (
), with the latest title and an indication of any unread news displayed. The latest 15 news items are displayed and more can be fetched by clicking on more at the bottom of the list.
Important news items will be highlighted and include a warning icon beside the title in the feed.