Using groups in section access and tabular reporting

dcz — Fri, 05 Sep 2025 13:59:40 GMT

Hello everyone,

We use SECTION ACCES to restrict access to applications, but it also allows us to automatically filter data for Tabular Reporting submissions. We modified the section that used USER.MAIL to use custom GROUPS.

After a few test report submissions, I see that the section access is no longer being taken into account, and all data is being sent.

Have I forgotten something? Or is it not possible to use section access to filter reports when USER.MAIL is not being used?

Access to the application works well using GROUP.

SECTION ACCESS;
Star is ALL;

NoConcatenate
Securite:
LOAD

'USER' as ACCESS,

'ALL'as USERID,

Code_BU as GROUP,

if(Identifiant = 'XXX' OR Identifiant = 'XXX' OR Identifiant = 'XXX'
OR Identifiant = 'XXX' OR Identifiant = 'XXX'
, 'ALL', REDUCTION) as REDUCTION
Resident Securite_temp;

// Drop table Securite_temp;

SECTION APPLICATION;

Re: Using groups in section access and tabular reporting

rohanthaakur — Mon, 15 Sep 2025 08:56:06 GMT

// Use custom (or both) groups in Section Access
SET QlikCloudGroupMode = 1; // 0=IdP, 1=Custom, 2=Both

SECTION ACCESS;
// Do NOT use "STAR IS ALL" here.
// List users or rely on GROUP, but don't wildcard USERID.

Securite:
LOAD
'USER' AS ACCESS,
Upper(Code_BU) AS [GROUP], // must match group claim
Upper(ReductionValue) AS REDUCTION, // links to data field
Upper(UserEmail) AS [USER.EMAIL] // optional but safest for reporting
Resident Securite_temp;

SECTION APPLICATION;
// Ensure the data model has the same REDUCTION field
// in the tables to be reduced.

topic Re: Using groups in section access and tabular reporting in Reporting Service & Alerting

Using groups in section access and tabular reporting

Re: Using groups in section access and tabular reporting