Administration

In this section:

  1. Understanding Administrator Roles and Privileges
    Administrator roles define the types of configuration, monitoring, and administration tasks that a user can perform in RUCKUS One.
  2. Generating an Application Token
    You can generate an application token to enable secure API communication between a third-party application and RUCKUS One. You can generate an application key and use the client ID and shared secret to authenticate the application for API usage.
  3. Configuring Privacy Settings
    An MSP Prime Admin may change the default privacy settings applied to all MSP Customers, Tech Partners, and HSP Brand Property tenant accounts.
  4. Configuring Email Notifications
    You can configure email notifications as a Managed Service Provider (MSP) to control how notification messages related to your networks, devices, and tenant activities are delivered. The email notification configuration determines which event types generate email alerts and which recipients receive them. You can also configure incident‑based and IntentAI‑based notification categories, including severity levels, descriptions, and AI‑driven event updates. This configuration allows you to customize the visibility and delivery of system notifications for all recipients associated with the MSP account.
  5. RBAC and ABAC Support
    Role-based access control (RBAC) and attributes-based access control (ABAC) are functionalities that provide a structured and efficient approach to managing administrator permissions and access rules in RUCKUS One.
  6. Setting Up RUCKUS One Login Access for SSO Group
    RUCKUS One has an enhanced administrative feature that allows SSO users to log in to RUCKUS One. In this method, users authenticated using Azure Active Directory (AD) are automatically provisioned according to the group in which they are members. This bypasses the need to directly add an individual administrator in RUCKUS One. You need to create an SSO Group by specifying the Object ID of the group defined in the AD, and assigning an RBAC role for the group. The individual users that belong to the specified group in the AD inherit the role assigned to the SSO Group and can use the AD credentials to seamlessly log in to RUCKUS One.
Parent topic: MSP User Operations