We are unable to create Private Locations in Splunk Observability Cloud using the documented API endpoint: POST /v2/synthetics/locations Although my user account has the admin role in the organization, organization access tokens cannot be assigned the admin role. The UI allows selecting only these roles: power read_only usage According to the documentation, these are the only roles available when creating org-tokens with API scope. Reference: https://help.splunk.com/en/splunk-observability-cloud/administer/authentication-and-security/authentication-tokens/org-access-tokens However, the ability to manage Private Locations via API ?requires? admin-level permissions, which are not included in the power/read_only/usage roles. Therefore, the API call fails due to insufficient permissions, even though the user who created the token is an administrator. User-role documentation: https://help.splunk.com/en/splunk-observability-cloud/administer/user-and-team-management/manage-roles We would like to clarify: Whether creating Private Locations using organization access tokens is officially supported. If yes, how we can assign the necessary admin-level permissions to the token. If not supported, whether this is an intended product limitation and whether support for this use case is planned. Whether the recommended workaround is to rely on short-lived user session tokens instead. This behavior prevents the automation of Private Location provisioning, even though the API endpoint is documented and intended for such use. ... View more