Hiding Data Module and Upload File Options

[MBLLLead]

Good Day,

When setting up my Cognos 11 enviroment we have decided to hide the Data Module and Upload File Options. We want to do this to start with, to help with transition and keep things simple for our basic users. I went into the administrative console and have remove the capabilities for these tools how ever my user can still see these options. Has anybody tried this before? and been successful

Thanks
MBLL Lead

[bus_pass_man]

Tried it and successful.  Set the web-based modeling and upload file capabilities.

Are your users members of roles or groups which still have been granted these capabilities? 

Is the everyone role in the permissions list?

Have you tried explicitly denying these capabilities?

Are there any users for whom your efforts have successfully achieved your desired goals?

[MBLLLead]

I have remove the capabilities for that user and those options still do not go away. I have also logged in as that user and check there capabilities under the option menu and these tools do not appear there.

Any other ideas???

MBLLLead

[bus_pass_man]

Yeah but some are dependent on the answers to the questions that I asked.  You just essentially repeated what you said in your first posting so there wasn't much advancement of knowledge.  Could you be kind enough to undertake the actions necessary to answer the questions in my original response please.

The chief idea is that I think it possible that your users are inheriting the capabilities from their membership of other roles which have been granted access.  If I was to bet, I would not be surprised if you have not removed the everyone role from its default grant access for the capability.   The default for any new role is to have everyone as a member so you'd need to check the modelers role's settings too.

The grant/deny functionality for any capability and any role is the same so these two capabilities should not be too much more intellectually challenging than the others.

One of my questions was to see if you had tried to explicitly deny these capabilities.  The explicit denial will override any explicit grant via another group or role.

A more mundane test-- browser cache refreshing  -- would be a good idea, too.  Log out as the user and then log in again.

An administrator, who would have access rights to the administration console via his ability to access the manage functionality, would be able to see the capabilities.   Whether some other user sees or not sees the capabilities is neither here not there.   In general it is probably a good idea to restrict the manage capability to only those users who need to work with them -- the administrators.   At the very least they ought to be knowledgeable enough to now that playing with sharp knives is dangerous and by limiting the numbers of people who can potter around the admin is useful. 

[MBLLLead]

I have remove all capabilities from that user. I have also tried denying that  user group capabilities and still does not work. I have ensured that the everyone group is not included in the capability set. I have tried logging in and out probably 15 times by this point. I am a administrator. We have a very small number of administrators and only those people can see the capabilities. Me included.

I do not think it is inheriting this from anything else. The reason i think this is when i go into the set preferences menu of the user i do not see upload file as a capability they have. I could see if it was listed here but it is not.

The one thing to note here is that we are currently on 11.0.0. We are going to 11.0.3 imminently so hopefully that might help.

[MBLLLead]

I install cognos in a new enviroment and it work. I will compare permission when i get a free day and see if i can notice any differences

[bus_pass_man]

I imagine that saying, well it works for me, although a true statement and one which advances the discussion by, its truth, establishing that it can be done, can be perceived differently; however it needs to be said.

I'm not altogether disabused of the notion that its a rights inheritance issue.

Is the everyone role showing up somewhere?

Are there any users for whom your efforts have successfully achieved your desired goals?

Are you sure that the users who are seeing upload files and data modules do not have those rights as members of other roles?  That would not show up directly.

[rverga01]

Hey bus_pass_man,

Thanks for this man, took a look at the capabilites that you said, simply removed the Everyone group. Voila, problem solved: Data Module Option Hidden.

Thanks.-

[prince9]

I install cognos in a new enviroment and it work. I will compare permission when i get a free day and see if i can notice any differences

When you are logged in as that user.  Check which groups and roles the user is member of...  Then check whether those user groups are part of 'upload files', 'web modelling'.

In my case I removed all groups and roles for those bits you are talking about and created custom groups.

Hope that helps!!!

[Mfg]

Hi @bus_pass_man,

What should we do to remove the "drag and drop your files or browse" UI box from the welcome page.

Why because even after disabling a upload file option for a user, the user is still able to see brows link active and once hit on it and selecting a file and then upload it then only error will display that the user do not have capability to upload file....!!!!

Please find the attachment for the same.

Thanks in advance

Mfg

[diab0lus]

Hi @bus_pass_man,

What should we do to remove the "drag and drop your files or browse" UI box from the welcome page.

Why because even after disabling a upload file option for a user, the user is still able to see brows link active and once hit on it and selecting a file and then upload it then only error will display that the user do not have capability to upload file....!!!!

Please find the attachment for the same.

Thanks in advance

Mfg

While I am not the requested user, I have found a working solution to this problem here and implemented it across my environments:

http://www.cognoise.com/index.php?topic=33628.0

It is worth restating that the above solution involves directly editing baseline html files that will likely become overwritten during a future upgrade, so it is a best practice to add this change to your documentation that tracks customization or start a document for that purpose if you don't already have one, because you will likely need to re-implement the change in future post-upgrade.

diab0lus

[CognosPaul]

While I am not the requested user, I have found a working solution to this problem here and implemented it across my environments:

http://www.cognoise.com/index.php?topic=33628.0

Love hearing when my work is helpful!

[diab0lus]

Love hearing when my work is helpful!

Very much so, thank you! Are the same CognosPaul that has the website by the same name?

[CognosPaul]

Only if he doesn't owe you money.