Permission to rename a Managed Collection

[RFS]

Why is renaming/renumbering a managed collection granted through administrative permission instead of modify identity?  With modify identity on documents, the user can use the "Rename" action menu item... but for a managed collection it isn't there unless I grant administrative rights to the role.  Which I don't really want to do because I haven't researched enough to see what else would be granted.

I am using WC 12.0.2.18 (upgrading soon, so if the answer is 'hey, just move to WC 13.x'... ok, I can live with it for a few more weeks)

[Fadel]

Hi , 

This is the way software is implemented , and its documented in  https://www.ptc.com/en/support/article/CS309711  .

99.99% same is on WC13 . 

[HelesicPetr]

Hi @Fadel 

Are you sure that the link is correct? What does a isodraw do with a Managed Collection? 

PetrH

[Fadel · Accepted solution]

There was a typo in link , here is it again https://www.ptc.com/en/support/article/CS309711 

[RFS]

Thank you for the link.  I believe I found it before.  My question was not "what permissions do I need"... it was "why do i need that?".  Is it by design, or an oversight not yet corrected?  Given how strict I can be with policies to control who could or could not modify identities of things, I'd like to be able to grant 1 small permission and not give out some demi-deity power at the same time.  

I hereby acknowledge this raised community issue was more of a gripe than a query.

[HelesicPetr]

Hi @RFS 

No one from PTC can say why. Because someone has designed it this way. 

PetrH

[Fadel]

Hello , this the way the software was implemented, if you need more info on the why , you can raise an TS call , a colleagues of mine will then get in touch with Product Manger and get back to you .

I don't think someone from the community has that piece of info .