TM1 Forum

Hi,

I wonder whether there's a way for a non-admin. to make an application object public after uploading it into Applications. Since the object by default is Private and even admin. can't see it to make it public.

Thanks.

Kenneth

Only admins can make objects public. Views within applications are simply short cuts to a view that exists in the cube. So as far as I'm aware the answer is no, unless something has recently changed. Allowing users to make objects public is something that's been requested many times before,

Jim.

jim wood wrote:Only admins can make objects public. Views within applications are simply short cuts to a view that exists in the cube. So as far as I'm aware the answer is no, unless something has recently changed. Allowing users to make objects public is something that's been requested many times before,

Jim.

Well actually within the specific confines of the application folders that's not true. If a user is a member of a group that has Admin rights to a folder then they can publish their own private shortcuts as public. (can't get around the issue of someone else's private links, have to seem something before you yourself can publish it).

In general it isn't being a (big A) Admin that matters for publishing a view or a subset (in general not withing application folders) but being a member of a group that has Admin rights to a cube or dimension. However the use case for giving a non-admin admin rights to a cube (i.e. they could in theory delete the cube) is tenuous, I haven't ever seen it enacted in practice as publishing views & subsets is the only benefit but the risks are many.

lotsaram wrote:

jim wood wrote:Only admins can make objects public. Views within applications are simply short cuts to a view that exists in the cube. So as far as I'm aware the answer is no, unless something has recently changed. Allowing users to make objects public is something that's been requested many times before,

Jim.

Well actually within the specific confines of the application folders that's not true. If a user is a member of a group that has Admin rights to a folder then they can publish their own private shortcuts as public. (can't get around the issue of someone else's private links, have to seem something before you yourself can publish it).

In general it isn't being a (big A) Admin that matters for publishing a view or a subset (in general not withing application folders) but being a member of a group that has Admin rights to a cube or dimension. However the use case for giving a non-admin admin rights to a cube (i.e. they could in theory delete the cube) is tenuous, I haven't ever seen it enacted in practice as publishing views & subsets is the only benefit but the risks are many.

lotsaram wrote: In general it isn't being a (big A) Admin that matters for publishing a view or a subset

Indeed, but I did say Admins rather than Admin.

lotsaram wrote: If a user is a member of a group that has Admin rights to a folder then they can publish their own private shortcuts as public.

Interesting. I've never tried that. So if it's a private view and a private application they can share it with everybody? Does it create a public version of the view or does it bypass that and just gives people access to the private view?

Thanks! I'll try test it out with giving a specific group admin. rights to certain folders in Applications.

Ken

jim wood wrote:Indeed, but I did say Admins rather than Admin.

I didn't think you were talking about the Admin user but I did take the following to mean you were talking about members of the Admin group.

jim wood wrote:Only admins can make objects public.

Maybe my interpretation isn't correct but that's what it reads like. To make an object public users don't need to be members of the admin group, they do need to be a member of at least one group that has Admin rights to the specific cube/dimension object in order to publish a view/subset.

jim wood wrote:So if it's a private view and a private application they can share it with everybody? Does it create a public version of the view or does it bypass that and just gives people access to the private view?

If its a view or subset it still needs to be public. But if a user has created a private application entry such as a shortcut to a view or loaded an Excel file which is for them private, then sure if they have Admin rights to the application folder then they can publish any objects in the application folder and make them public.

kenship wrote:Thanks! I'll try test it out with giving a specific group admin. rights to certain folders in Applications.

NP hope it solves your issue. You do realise though that this applies only for a user publishing their own private application entries as public? Entries which are someone else's private links can only be seen by them and so can't be published by someone else.