In Qlik Sense, attributes are referred to as properties. Properties are used to identify the user who is requesting access, the resource that is impacted by the request, and the environment from which the request is made. In Qlik Sense you can use default property types that are supplied out-of-the-box, properties supplied by the directory services through user directory connectors, or you can define your own customized properties.
Default properties
Qlik Sense provides default properties that you can use to describe the subject (user), environment, and resources. In the example One property-value pair in conditions:, the user group membership (AD group) was used as a property to identify the user. We could also have added an environment property, such as IP or request type, to limit the access to one or more IP addresses or HTTPS request types, respectively.
Directory services properties
As you connect Qlik Sense to directory services, using user directory connectors in the QMC, the user properties from the directory services will be made available to you. You can see the properties in the user condition drop-down list when you create rules.
Custom properties
Custom properties enable you to define properties of your own and assign possible values. This enables you to complement default environment properties with properties of your own. Custom properties also enable you to work with user roles or types.
For example, you may have Qlik Sense developers, contributors, and consumers in your organization. Let's assume that these user types are not defined as groups in your directory service. With custom properties you have the option of defining a UserType property. You can then assign the possible values Developer, Contributor, or Consumer to your users and apply rules per user type instead of applying them to individuals or to user group memberships.
You can see the custom properties in the user condition drop-down list when you create rules. Custom properties have the "@" suffix in the list.
Examples:
Security rules example: Applying Qlik Sense access rights for user types