Network Management

Create a SolarWinds Platform user with access only to IP Address Manager (IPAM)

This article describes how to create a SolarWinds Platform web console user who can access only IP Address Manager (IPAM) and is restricted from administering or using other SolarWinds Platform modules.

First published date

3/3/2026 5:31 PM

Last published date

3/3/2026 5:38 PM

Overview

You need to create a user account that has access only to IPAM and does not have administrative or functional access to other modules like NPM, SAM, etc.

Product section

IP Address Manager

Resolution

Solution

1. Create the SolarWinds Platform account

  1. In the SolarWinds Platform web console, navigate to:
    Settings > All Settings > Manage Accounts.

  2. Click Add New Account and create the user account as needed (Windows, AD, SAML, or local account).

  3. Ensure the global “Administrator / Allow administrator rights” option is not enabled for this account.

This ensures the user starts with limited, non-admin access by default.

2. Restrict access to other SolarWinds Platform modules

  1. While still editing the same account, review permissions for other modules (for example, NPM, SAM, etc.).

  2. Keep the default limited permissions and do not grant admin or power-user rights in any modules other than IPAM.

  3. (Optional) Use Customize Menu Bars to assign an IPAM-focused menu bar so the user does not see navigation items for other product views.

This keeps the user’s view focused on IPAM and prevents access to features from other modules.

3. Grant IPAM-specific permissions

  1. On the same account configuration page, scroll down to the IP Address Manager Settings (IPAM) section.

  2. Under IPAM settings, assign an appropriate IPAM role to the user:

    • Read Only – view-only access to IPAM data.

    • Operator – can manage IP ranges/status/properties where allowed.

    • Power User – includes Operator capabilities plus subnet/supernet management and scans.

    • Administrator – full IPAM control, including DHCP/DNS management within IPAM.

  3. Click Save to apply the changes to the account.

The user will now be able to log in and work only within IPAM, according to the assigned IPAM role.

Additional Notes

  • If the user should see only IPAM-related pages, double-check the assigned menu bar and views to ensure non-IPAM views are not exposed.

  • Changes to account roles or IPAM permissions may require the user to log out and back in to see updated access.