qlik-security
Section access patterns, row-level security, data reduction, OMIT field usage, hybrid security models, and Cloud vs. client-managed security differences. Use when designing or reviewing security configurations.
Install
With your agent
Install OMGSkills skill "pupfish-llc/qlik-agents:skills/qlik-security" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Pupfish-LLC/qlik-agents /tmp/qlik-agents && ln -s /tmp/qlik-agents/skills/qlik-security ~/.claude/skills/qlik-securityFrom README
Qlik Security Overview Security in Qlik Sense controls which data users can view. Section Access is the primary mechanism—it filters rows and hides columns at load time, before the user interface loads. Unlike runtime filtering, section access works invisibly: a user with restricted access simply sees a different model. This makes section access powerful but also error-prone; misconfigured access rules often fail silently, appearing to work while exposing or hiding unintended data. Section access is required for any app with multiple users, PII protection, compliance regulations (GDPR, HIPAA), or data tenancy. The configuration differs significantly between Qlik Cloud and client-managed deployments. Cloud uses email-based identity and OIDC/SAML provisioning. Client-managed uses Windows domain authentication (NTNAME, DOMAIN\Username) with manual user lists.