Hi ​@Satya where exactly are they trying to locate/view the component? Could you make a screenshot of what you see vs what another user sees?

Thank you!

Hi ​@Lisa Kovalskaia , they are not able to find the component either on web or desktop. Search results are empty.

But VCI is visible both on web and desktop to everyone in the team

.

HI ​@anna.spakova, ​@Cansu  Any help on this!

Hi ​@Satya ,

can you confirm if the users donwloaded changes in the ONE Desktop tool (using refresh on the connection, disconnect/connect back to it)? If you say - they can see the VCI in ONE Desktop, can you send a screenshot of that? They see an old version or what do you mean by that? Can they right-click and run Download? That can also download updates on it.

Other than that, I can only think of permissions on the components → if you navigate in the UI to Components and track down the relevant Transformation (VCI) one, you can check who has access to it:

Let me know if any of this helps please.

Kind regards,

Anna

Hi ​@anna.spakova, 

I have checked the access in UI, surprisingly VCI is created with full access to entire group whereas its component is created with individual user access to me alone.

Please let me know if anything can be done while publishing component to give access to entire group?

Hi ​@Satya ,

all VCIs belong under some source so it is likely that in your case the VCI inherits the group permissions from this data source. If you open the share options in the VCI, you can see the groups with the lock symbol - if you place the mouse cursor on it, it will tell you how is the access inherited:

However, in case of components, there is no parent object that would give access to all components automatically. So the access is only given to the creator user who becomes the owner of it, and this user then needs to share the component manually with other users/groups that should have access to it as well. That can be done using the share button. 

To automate this, I can think of only some orchestration process using a notification handler, which would require some effort to implement. In short, when a new component is created, a workflow on the orchestration server would be triggered that would share the component automatically. But components are usually quite technical, and only a handful of users usually require access to them. So it might not be worth the effort. But let me know if this is something interesting for you, and I can share links to more resources about this topic.

I hope it is clear now, but let me know if you need further information.

Kind regards,

Anna