Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details

Qlik Automate: Oauth Client with "automations.admin" scope, gets "403 insufficient permissions" when running automation in a Shared Space

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Daniele_Purrone
Support
Support

Qlik Automate: Oauth Client with "automations.admin" scope, gets "403 insufficient permissions" when running automation in a Shared Space

Last Update:

Jul 2, 2025 5:12:29 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jul 2, 2025 5:12:29 AM

An OAuth client has admin.apps, admin.automations and admin.spaces scopes.

When using it with API calls to run automations in a shared space, the result is 403 insufficient permissions.

The assumption is that the admin scopes should be enough to execute the automation.

 

Resolution

Explicitly add the OAuth client as a user on the tenant and give the user Can manage permissions. 

add OAuth client as user with can manage permission.png

Cause

It is the same concept as a Tenant Admin.

A Tenant Admin can see everything, but to open apps in a space or reload them, the admin user must be explicitly added to the space.

The same concept applies to the OAuth admin scopes.

 

 

Environment

  • Qlik Automate
  • Qlik Cloud
Labels (1)
Version history
Last update:
‎2025-07-02 05:12 AM
Updated by: