--- title: "Creating an SDP Admin or API User and Determining the Correct Privileges" slug: "creating-an-sdp-admin-or-api-user-and-determining-the-correct-privileges" description: "AppGate enables granular admin roles for secure access control, ideal for API automation and limited dashboard access. " updated: 2026-01-07T16:21:02Z published: 2026-01-07T16:21:02Z canonical: "support.appgate.com/creating-an-sdp-admin-or-api-user-and-determining-the-correct-privileges" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Creating an SDP Admin or API User and Determining the Correct Privileges AppGate SDP allows you to create Admin accounts with granular access controls to limit connections to resources that users are not required to access. Most common use cases are for API accounts used in task automation, and restricted Admin access for other teams that have some responsibility in the system, like a Security Operation Center (SOC). The roles are configured in the SDP Admin user interface at System > Admin Roles. These roles can then be assigned to an Admin policy that can be assigned to a user. The user can be from an account from an Identity Provider (IDP), or from the local user database, and the role is assigned to the policy received by the user. Admin roles define the privileges (e.g., editing Policies, deleting Policies, revoking tokens, etc.) that can be performed from the Admin UI. Admin roles are assigned to administrators using Policies in the same way as user . The Admin roles for each administrator are listed in their Entitlement token once they have logged into the Admin UI, and remain valid until the session ends (i.e., until they sign out), the Entitlement token expires, or the Entitlement is renewed (whichever occurs soonest). The AppGate SDP Admin Guide provides details on how to add [Admin users](/v1/docs/admin-user-access-v6-6#steps-to-configure-additional-administrators) and assign roles. ## Configuring Admin Roles ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/creating-an-sdp-admin-or-api-user-and-determining-the-correct-privileges-image-eux4udj3.png?sv=2026-02-06&spr=https&st=2026-10-27T02%3A41%3A19Z&se=2026-10-27T03%3A41%3A19Z&sr=c&sp=r&sig=6MIySY2K%2ByIzyleeLYvabvbDBIuMIwl%2B6Q1pW3ivVb4%3D) ## [Admin priviledge](/v1/docs/admin-user-access-v6-6#steps-to-configure-additional-administrators)s - Limited Dashboard Access Access to the SDP Admin Dashboard works slightly differently from other single-function pages, as it contains a number of Target Items. Limiting Dashboard Access means an admin may have only partial access to the information on the Dashboard (e.g., privileges to see user sign-in and on-boarded device information, but not Admin Messages or Appliance information). ## Full Dashboard access For full dashboard access, the following privileges are required: • privileges on • privileges on • privileges on • privileges on (for user-sign-ins) • privileges on • privileges on A defined access right or permission granted to users or devices, allowing them to access specific resources or functionalities within the Appgate ZTNA system.