Qlik Community

Security & Governance

Discussion board where members can learn more about Qlik Sense deployments which are governed and self-service.

Announcements
Read about the latest Qlik Community enhancements on the Community News blog!
cancel
Showing results for 
Search instead for 
Did you mean: 
EndreNTillung
Partner
Partner

Section Access Qlik Sense SaaS

Hi,

 

Is it possible to use wildcards in the field User.Email for Section Access in Qlik Sense Saas?

For example, is it possible to grant access to every person that has an email ending with "@123.com", without having to type out every single email in Section Access? What I want is something like this:

Section Access;
LOAD * INLINE [

ACCESS, USERID, USER.EMAIL, REDUCTION

USER, *, *@123.com, A

USER, *, *@abc.com, B

];

So emails ending with "@123.com" has access to "A" and emails ending with "@abc.com" as access to "B".

 

Regards,

Endre

1 Solution

Accepted Solutions
Dalton_Ruer
Employee
Employee

No the wildcard is simply used for all instead of identifying the email addresses. Like ALL authenticated users. 

If you aren't using the Qlik Identity Provider for your IDP, and aren't in Qlik Cloud Business you could utilize the GROUP field. Simply put all 123.com users in Group 1 and abc.com users in Group 2. 

If you have access to your user list, meaning you know all users and their emails, you can populate the Section Access stuff on the fly from a table that has it. So you would generate all users with A and B etc. 

View solution in original post

1 Reply
Dalton_Ruer
Employee
Employee

No the wildcard is simply used for all instead of identifying the email addresses. Like ALL authenticated users. 

If you aren't using the Qlik Identity Provider for your IDP, and aren't in Qlik Cloud Business you could utilize the GROUP field. Simply put all 123.com users in Group 1 and abc.com users in Group 2. 

If you have access to your user list, meaning you know all users and their emails, you can populate the Section Access stuff on the fly from a table that has it. So you would generate all users with A and B etc. 

View solution in original post