Skip to main content

Troubleshoot: An Admin Can't See or Edit a Resource

An administrator tells you that a Privileged Access Management (PAM) resource is missing from the Admin Portal, or that they can see it but cannot change it. In almost every case, the cause is how PAM controls which administrators manage each resource. This article explains the rules and shows how to fix the access.

An administrator does not see a resource, or can see it but cannot edit it.​

Two things decide what an administrator can do with a resource: the role of the administrator, and the list of managers of the resource.

What decides itWhat it controlsWhere you set it
RoleWhich areas of PAM the administrator can use, and whether they can view, create, update, or delete in each area.Settings > Administrators
Managers of the resourceWhich individual resources the administrator can see and manage.The Managers card in the edit screen of each resource

The rules are:

  • Administrator with Billing sees and manages all PAM resources.

  • Any other administrator sees and manages only the resources that list them as a manager. An administrator is a manager when they are added directly to the resource, or when they belong to a Resource Manager that is added to the resource.

  • The exception is a role with the Manage all Privileged Resources permission. It manages every resource, even those that do not list the administrator.

note

Managing a resource is different from connecting to it. To connect, the user must belong to a user group that has access to the resource.

Symptoms: An administrator does not see a server, a database, a website, or a credential in PAM. Or the administrator sees a resource but cannot edit it.

Resolution: Complete these steps with an administrator who can manage all resources, such as an Administrator with Billing.

  1. Check the role of the administrator. In the Admin Portal, go to Settings > Administrators. If the administrator has the Administrator with Billing role, they already see all resources, and this issue does not apply.

  2. Go to Access > PAM > Privileged Resources. Open the resource that the administrator cannot see or edit.

  3. In the Managers card of the resource, check the Resource Managers and Admins tabs. The name of the card follows the type of the resource, for example Server Managers.

note

Placeholder screenshot: Server Managers card of a server with the Resource Managers tab and the Admins tab

  1. Give the administrator access in one of two ways:

    • Directly: on the Admins tab, add the administrator.

    • Through a Resource Manager: on the Resource Managers tab, select Add Resource Managers and add a Resource Manager that includes the administrator.

  2. If the administrator sees the resource but cannot edit it, check the permission in the Permissions column. View Details lets the administrator only view the resource. Manage lets the administrator edit it. To change a Resource Manager permission, see Edit Resource Manager Permissions.

  3. Save the resource, and ask the administrator to check again.

tip

Use Resource Managers. Add the administrators to a Resource Manager and add the Resource Manager to the resources. This avoids editing each resource when the team changes. See Delegate Resource Management with Resource Managers.

Limit Manage all Privileged Resources. This permission bypasses the managers of every resource. Give it to a few administrators.

Grant the minimum. Start with View Details, and add Manage only to the resources that the administrator must change.

The PAM menu is missing.​

Symptoms: An administrator does not see the PAM menu in the Admin Portal.

Resolution: The role needs View on Application Management > Applications. View does not let the administrator change SSO applications. It only shows the PAM menu. Edit the role of the administrator and add the permission. For the steps to create or edit a role, see Create a Custom Admin Role for PAM.

One area of PAM is missing.​

Symptoms: An administrator does not see one area of PAM, such as Resource Managers or Jump Servers.

Resolution: The role needs at least View on that area. Edit the role of the administrator and add the permission. For the steps to create or edit a role, see Create a Custom Admin Role for PAM.

The administrator manages the resource but cannot connect to it.​

Symptoms: The administrator can manage the resource in the Admin Portal, but cannot connect to it as a user.

Resolution: Managing a resource does not give access to connect. Add the administrator to a user group that has access to the resource.

What PAM access do the default roles include?​

Symptoms: You need to know which default roles can use PAM. For the complete list of roles, see Admin Portal Roles.

Resolution: The default roles have these PAM permissions:

RolePAM access
Administrator with BillingFull access, including Manage all Privileged Resources and Backup.
AdministratorEdit access to resources, Resource Managers, Blocking Rules, Jump Servers, and User Groups, plus Overview, Session History, and Backup. It does not include Manage all Privileged Resources.
ManagerEdit access to websites, servers, databases, credentials, and Resource Managers only.
Read OnlyView access to Overview and Session History.
Command Runner, Command Runner with Billing, Help Desk, Billing Only, Asset ManagerNo PAM access.

Was this information helpful?