If you are using QlikSense Enterprise, you will probably know that one or more people can access an application you just published in a stream.
Tipically, someone can access to stream (and all its respective applications) only if there is a specific security rule that allows it.
You just created a new stream called Example and you want several people of several divisions access this stream; you can achieve this in different ways, for example:
- type each user while creating the security rule
- define a custom property and assign it to the interested people
First of all, let’s create a new stream!!
Clicking on Apply you will notice this screen
If your first thought on seeing this is ” what the f*#? ” don’t worry, let’s see what each section means:
- Name: is the name of the security rule you are going to create
- Description: is a short description of the security rule you are going to create
- Resource filter: this represents the resource that should be accessed after you create the security rule (in this example, the resource is a specific Stream ID, which is the ID of the Example Stream)
- Actions: if you will be able to access a specific resource, you could have differnt permissions, for example publish (in this example, you could publish a new app in the Example Stream)
In the end you have a user-friendly and an advanced boxes; all the thing you are going to type in one box, will be replicated on the other… basically, if you are feeling confident with the security rules, you could easily type on the advanced box, otherwise I suggest you to use the user-friendly box.
Before I suggested you two ways you can allow people can access the Example stream:
- type each user while creating the security rule
If you need Marco Giannuzzi to access the Example stream, you can easily type the user you want in the user-friendly box, in the detail
You now need to add another user? No worries! You can press the + button and it will appear a new condition.
Using this approach, you have to access everytime to this security rule if tomorrow… in one week/month/year you have to guarantee another user can access the Example stream.
This is the reason why I really suggest you to use this second approach
- define a custom property and assign it to the interested people
A custom property (link) in this context is pretty useful since it allows the creation of a “virtual group”; moreover, a custom property can be assigned to one or more people and you assure they can access a particular resource (in this case, a stream).
Let’s create first of all a new Custom Property! (for a more detail, click here)
This custom property will be applied only on user resources, so you will put a flag only on ‘Users’.
As name we can type everything you want, even if I like to use Stream as a name, since this custom property will be useful to access a specific stream.
The value is the most important parameter in this custom property since all the possible values it can assume will be the interested streams names!
More in the detail, in this example we will create a new value called Example, just as the stream we previously created!
After creating the user custom property, let’s go back on the stream’s security rule:
As you can see, in the user-friendly box there isn’t the “name” parameter since in the dropdown we just selected @Stream and it’s the custom property we just created!
After creating a custom property and a security rule, we have only a step: assign the custom property to the users! This can be achieved basically using the Users section
After selecting the desidered user(s) , you can double click and expand the “Custom Property” section; you will notice there is the Stream custom property we just created and you can enter as value(s) the desidered stream name.
This will guarantee that this user will be able to access to the Example stream and, if in the future you need another user to access the stream, you don’t have to go on the security rule; you will only have to find the new user and assign it the custom property!
Trying to synthesize the two approaches:
- Security rule without custom property
- Create a stream, you can use any name
- Create a security rule using as criteria all the desidered names, one by one
- Security rule with custom property
- Create a custom property called Stream and apply it to the user resources, entering as value the desired stream name (if you already created the Custom Property and you want to create a new stream rule, you have to assign another value!)
- Create a stream, entering as name the value used in the custom property
- Create a security rule using as criteria the user Custom Property
- Assign the custom property to the desidered user(s)