Functions of internal users in Qlik Sense

[purpleliar]

Hi everyone,

I've tried to search info about internal users of Qlik Sense (sa_repository, sa_scheduler, sa_qlikview, etc.) and their functions  but I couldn't find them.

Could you help me please?

Thanks in advance!

Best Regards

[Jay_Brown]

Hello @purpleliar , INTERNAL\sa_XXX accounts are our internal service accounts and are used for internal system processes. 

If you keep in mind the above, these are somewhat self-explanatory;  sa_repository is the internal repository service account, sa_proxy is the internal proxy service account, sa_converter is the internal converter service account, and so on.

As you noted there is no documentation around this because in general, they should not be used except where documented, for example here.



Hope that helps!

[PadmaPriya]

Hello @purpleliar 

• INTERNAL/sa_repository: This makes the section access script available with the repository service for controlling user access.

• INTERNAL/sa_scheduler: This allows the app to reload using QMC tasks. (Internal\sa_scheduler mandatory to reload apps with section access from Qlik Sense QMC)

Please have a look at the below article:

https://community.qlik.com/t5/Official-Support-Articles/Internal-sa-scheduler-mandatory-to-reload-ap...

Thanks,

Padma Priya

Qlik Support

[purpleliar]

Thanks @Jay_Brown and thanks @PadmaPriya 

Is possible to know the function of the user sa_qlikview?

Thanks

Best Regards

[PadmaPriya · Accepted solution]

Hello @purpleliar 

QlikView SA Account:

It is a feature used to control the security of QlikView applications. Section access is defined as part of the load script, where we define an authorization table, i.e. a table where you define who gets to see what information and from where. Section access can be of various types, depending on the sensitivity of the information and business comfort:-

1. A simple username and password might be sufficient to access some documents
2. In some scenarios, you would want specific users in your domain to be logged in specific machines and use certain keys to unlock the information.
3. You may also want to restrict access to specific objects and sheets of a document.
4. Remove fields from the data model for the specified user (by omitting them).
5. Row level data reduction based on authorization mentioned.

Thanks,

Padma Priya

[purpleliar]

Thanks @PadmaPriya 

Very clear and complete.

Best Regards

[PadmaPriya]

Thanks for your response @purpleliar 

Have a great day ahead!

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!

[Amy-M-Collins]

Hi @Jay_Brown ,

Thank you for this, very helpful! 

In my environment, these accounts are allocated 10 of my license tokens. I have limited tokens and much demand for them. Furthermore, if they are necessary for the service to function, why do they to be allocated a license?

Is is safe to de-allocate a license from some of them? Or, am I missing something important?

Thanks in advance!

[Jay_Brown]

Hello @Amy-M-Collins , should not be necessary to have a license allocated to these INTERNAL\sa acounts.

Check your license allocation rules and make sure one does not exist for INTERNAL\ as well.