Hi,

Can someone explain to me the purpose of the Capabilies setting on Folder level ?

Creating a folder within the Team Folder you can set some properties.
There is a Capabilities TAB, but it looks like, Cognos ignores anything you configure here.
I know deny overules the allow, but it looks like it's not checking the folder capabilities settings.

Does anyone knows about this 'functionality' ?

Kind Regards,



------------------------------
Chris Bos
------------------------------

#CognosAnalyticswithWatson

Hi Chris
This purpose is to have the Capabilities setting be more granular.

For example if I have a specific package or folder of packages that I don't want to be used with Event Studio I can deny them.




If there is a specific capability and/or version we need to look at please let me know.

Thanks,


------------------------------
TREVOR COMEAU
------------------------------

Hi Chris,

I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. If Cognos seems to ignore the setting, maybe the underlying objects are not configured the same way. Does this makes sense?

Regards,
Peter

------------------------------
Peter Brusse
------------------------------

I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse
------------------------------

Hi Peter,

It would make sense if it was working.
I setup on folder level the required settings including the lower folders.
But it looks like Cognos is not looking at these settings.

Kind Regards,

------------------------------
Chris Bos
------------------------------

Original Message:
Sent: Mon May 17, 2021 04:27 AM
From: Peter Brusse
Subject: Capabilities on Folder Level


I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse
------------------------------

Off-topic: seems that the IBM site placed my reply a couply of times..it wasn't that great ;).

On-topic: I tried this at my current environment.
For example, on most folders, the Report Studio capability isn't allowed, so we set the capability permission to neither grant or deny).
That way, when the user right-clicks on a certain report in that folder, there isn't a 'Edit report' option as expected.
We did use the Everyone group..maybe the user belongs to several groups and therefore are in conflict?

------------------------------
Peter Brusse
------------------------------

Original Message:
Sent: Mon May 17, 2021 03:27 PM
From: Chris Bos
Subject: Capabilities on Folder Level

Hi Peter,

It would make sense if it was working.
I setup on folder level the required settings including the lower folders.
But it looks like Cognos is not looking at these settings.

Kind Regards,

------------------------------
Chris Bos
------------------------------


Original Message:
Sent: Mon May 17, 2021 04:27 AM
From: Peter Brusse
Subject: Capabilities on Folder Level


I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse

Hi Peter,

Thanks for the reply again.

Based on your post I found out what going wrong.
Using the 'everyone' group does work, but that's not what we have and need.
We have some different groups we need to give other capabilities and apparently that's not possible.

Back to the drawing board and another way.......

Kind Regards,

------------------------------
Chris Bos
------------------------------

Original Message:
Sent: Tue May 18, 2021 02:41 AM
From: Peter Brusse
Subject: Capabilities on Folder Level

Off-topic: seems that the IBM site placed my reply a couply of times..it wasn't that great ;).

On-topic: I tried this at my current environment.
For example, on most folders, the Report Studio capability isn't allowed, so we set the capability permission to neither grant or deny).
That way, when the user right-clicks on a certain report in that folder, there isn't a 'Edit report' option as expected.
We did use the Everyone group..maybe the user belongs to several groups and therefore are in conflict?

------------------------------
Peter Brusse
------------------------------


Original Message:
Sent: Mon May 17, 2021 03:27 PM
From: Chris Bos
Subject: Capabilities on Folder Level

Hi Peter,

It would make sense if it was working.
I setup on folder level the required settings including the lower folders.
But it looks like Cognos is not looking at these settings.

Kind Regards,

------------------------------
Chris Bos


Original Message:
Sent: Mon May 17, 2021 04:27 AM
From: Peter Brusse
Subject: Capabilities on Folder Level


I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse

I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse
------------------------------

I thought a possible use-case for this could be, that for example you want to prohibit end-users to use Report Studio or certain export formats on specific folders/reports; but you do want to have those permissions/capabilties on other folders/reports. Maybe if Cognos is ignoring the setting, the underlying object have different capabiltity settings?
Does this makes sense

Regards,
Peter

------------------------------
Peter Brusse
------------------------------