Thank you, Stuart, for your reply
We are using AD, but previously, for the TM1 app, we configured and managed users and groups within the Cognos environment. This environment is a bit rough, missing oversight on who is connected to what, and so on. Therefore I moved this configuration into a PA (TM1) cubes and overrode the }ClientGroups security wit a cube rule
['}Groups':{'ADMIN','DataAdmin','OperationsAdmin','SecurityAdmin','CAMID("::Everyone")'}]=S: STET;
[] = S:DB('Security_ClientGroups', !}Clients, !}Groups,'CAMID');
In PAW, I now have a complete overview of who is connected to what group and dimensions, and I can now use the great drilling and filtering within PAW. Now I need a better way to configure the PAW users and groups, somewhat in relation to PA users and groups.
Problems with the current setup in PAW:
If anyone within our domain is automatically imported in the Workspace during CAM login, then we have a lot of unwanted users (a lot of trash), and default access must thus be restricted to nothing.
An alternative to TM1 application sheet security wanted:
In one TM1 model, we had some 30 sheets in the old application, and users only got to see the sheet if they had access to some of its data. As I understand, this functionality can not be replicated within the PAW environment. The solution is then to create several books and manage their access with PAW groups. This means that PAW groups must be related to PA data access groups. I could add this configuration to my PA cube described above, but then the data sink with PAW users and groups is missing.
Can you please suggest a solution for me?