Skip to main content
Announcements
Introducing a new Enhanced File Management feature in Qlik Cloud! GET THE DETAILS!
cancel
Showing results for 
Search instead for 
Did you mean: 
chandrasjr1
Contributor II
Contributor II

Section Access Username syntax in Cloud

Hi All,

In Enterprise I use below format

 

***************

Section Access;
LOAD * INLINE [
ACCESS, USERID
ADMIN,UD\EMAIL.COM
];

Section Application;

***************

 

Here UD= User Directory from QMC UDC

 

In cloud, how to find the right format to use. I tried couple of combinations such as email (same case similar to how it appears in my profile (mix of small & caps), all in small & all in caps)

 

I am receiving "Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script." error.

 

Labels (2)
1 Solution

Accepted Solutions
marksouzacosta

Hi @chandrasjr1 ,

Qlik Cloud uses different fields for Section Access.
Use the field USER.EMAIL instead of USERID:

Example:

Section Access;
LOAD * inline [
ACCESS, USER.EMAIL
ADMIN, USER1@EXAMPLE.COM 
USER, USER2@EXAMPLE.COM 
USER,  
];

Section Application;

To check your email address, you can click on the icon on the top right corner of Qlik Cloud.

mark_costa_0-1709069672815.png

 

 

More details on Qlik Help:
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Scripting/Security/manag...

Read more at Data Voyagers - datavoyagers.net

View solution in original post

2 Replies
marksouzacosta

Hi @chandrasjr1 ,

Qlik Cloud uses different fields for Section Access.
Use the field USER.EMAIL instead of USERID:

Example:

Section Access;
LOAD * inline [
ACCESS, USER.EMAIL
ADMIN, USER1@EXAMPLE.COM 
USER, USER2@EXAMPLE.COM 
USER,  
];

Section Application;

To check your email address, you can click on the icon on the top right corner of Qlik Cloud.

mark_costa_0-1709069672815.png

 

 

More details on Qlik Help:
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Scripting/Security/manag...

Read more at Data Voyagers - datavoyagers.net
chandrasjr1
Contributor II
Contributor II
Author

Thank you. Using "USER.EMAIL" made the trick 🙂