Support sheet for admins - how to see all users?

[#1]

Hi,

I have a working section access.

I would like to have a support sheet that will be reachable on the Access Point with a separate Bookmark. My question is now, how can I create the table in the data model, with the current implementation the NTNAME gets reduced to only show my own user. But I would like to click on any user's name to see what he is able to see when logged in.

Is that possible?

Thanks.

[#2]

Anybody who can help?

[marcus_sommer]

It's not quite clear what do you want to do. Create a separate application with an overview to the access of all other applications and users or integrate this into each single application? Want you see the access to the applications and/or restrictions per section access? Are you using NT or DMS as authentification mode?

Generell are there these data available you could restrict the access only to you. Maybe these tools especially the user manager within the powertools are helpful for you:

http://community.qlik.com/blogs/technicalbulletin/2013/12/05/qlikview-governance-dashboard-11-availa...

Governance Materials.zip

PowerTools 1.1 for QlikView

- Marcus

[#4]

I would like to have a copy of the invisible section access table in the data model of my single application. I'm using link tables, as I'm reducing on two fields during section access, and I would like to connect this copied table with the link tables.

I'm using NTNAMES for authentification.

[marcus_sommer]

I have done something similar by loading the section access table twice. First as normal section access and then as section application again and use there another key to my link table. This meant my link-table had two keys. One for the section access and one for my visibility.

The access to this table isn't strict restricted then everybody by us knows the main-logic how the restrictions worked and it's no secret. Nevertheless this table is on a hidden sheet with osuser() = OnlyMe. This is enough and the most user would never try to search for data which are independent to their business (fields are generally available). But I think it would be possible to link these visible table also to the section accessSection Access

Alternatively you could read the section access from all your applications in a special applications so that you could have a central overview ...

- Marcus

[#6]

Hi Marcus,

I still had no luck solving this. By reloading the section access table in the application part, I either have the situation that my Admin still cannot see everything (at least not other users than himself) or that the normal users can see everything, so reduction does not work.

I attached my script with working section access, it is only a model of the real application.Could you please help me? What has to be done to load the acces information in the application?

Many thanks

Jens

[marcus_sommer]

In your way you have two identically tables - one within the section access and one within the section application. This will create synthetic keys and circular references between those both tables and your table with the linked dimension. But if you used a qualify-statement for the table within the section application - it should work. To see how the datamodel looked like within the tableviewer you could comment the section access statement.

An alternatively could be to store these table as qvd - with an additionally documentname() - and then drop the table and load the qvd in a special admin-app. This had the advantage of a central overview to all section access restrictions in your environment.

- Marcus

[#8]

Thanks for your response Marcus.

I will give the "Qualify" solution a try - see what's happening .

The special-admin app is not really an option, the application I'm currently working on will remain the only one on that QV installation. So I think it is easier to have the overview in the same appliction on a separate sheet.

Jens

EDIT:

After trying the Qualify solution. I don't get the idea behind it, to be honest. What I was planning to do to drop the table Access_TMP (which is my preparation table for the SA). Then I have the Section Access table itself with the fields ACCESS, NTNAME, PARTY_AUTONUM and TERRITORY_AUTONUM. I would reload the Access_TMP as Access (before dropping it of course) with ACCESS_TMP, NTNAME_TMP, PARTY_AUTONUM_TRY and TERRITORY_AUTONUM_TRY.

The attached screen is from the Qualify solution, I think i'm missing something. Help me, please .

[marcus_sommer]

Your datamodel looked quite right - if you loaded the Access_TMP within the section access part it should work.

- Marcus

[#10]

The section access itself works fine this way.

The problem is, that the admin user can only see himself in the published dashboard as NTNAME.

So I added the following to the section application:

     LOAD

          NTNAME as NTNAME_TMP,

          PARTY_AUTONUM,

          TERRITORY_AUTONUM

     Resident Access_TMP;

     drop table Access_TMP;

This (nearly) works. The admin can then see all users and all related PARTY_IDs, he sees all TERRITORY_IDs, but not the related users.

Again, the data reduction is working fine. User 'A' is reduced to his territory 'ABC' and can only see his data. But the admin does not see the relationship between 'A' and 'ABC'.