Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

What user rights are required to do a workspace sync?

awatt
Advocate

What user rights are required to do a workspace sync?

awatt
Advocate
Advocate

I've done some limited testing, but it seems my admin accounts can perform a workspace sync, but standard users can't. for regular users, the workspace sync operation scans the local files, but doesn't compare them to the Vault and returns 0 deletions and 0 downloads no matter the condition of the workspace.

 

Is there a role / permission they're lacking perhaps?

0 Likes
Reply
Accepted solutions (2)
473 Views
12 Replies
Replies (12)

awatt
Advocate
Advocate

Through tedious trial-and-error, I've found the missing permisison was 'Access Cloaked Objects'.

 

Is this documented anywhere? Seems important.

0 Likes

ihayesjr
Community Manager
Community Manager

@awatt 

Not being able to see Cloaked objects should not affect Workspace Sync.

A clocked object is one in which a user doesn't have the Read Permission set. You don't want to give that permission to all users.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes

awatt
Advocate
Advocate

One would think so, but. . .

 

I created a cutom role with only 'Access cloaked objects'.

 

When I assign that role to a regular user, workspace sync works.

When I remove the role, it doesn't.

 

 

0 Likes

ihayesjr
Community Manager
Community Manager

What roles does the regular user have?




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes

awatt
Advocate
Advocate

The Group is assigned:
Change order Editor (Level 1),
Custom Object Consumer
Document Editor (Level 2)

Document Manager (Level 2)

 

Vault authentication 

Vault Pro 2024
No replication

0 Likes

ihayesjr
Community Manager
Community Manager

I have set up a user with the same roles and can get Workspace Sync to work.

Can you create a support ticket for this? You really do not want to give all your users that permission.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes

ihayesjr
Community Manager
Community Manager

@awatt 

By the way, when you show that it has zero downloads, do they have old versions of the files in their workspace, currently?

If not, remove that custom role from a user. Make sure you have an old version of a file in the workspace. Then try Workspace Sync.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes

awatt
Advocate
Advocate

Yes, I deliberately download an older version before each test, with version priority not revision. But without the additional rights it scans the local files and stops, never even looking at the vault.

Case number 00789220 has been submited to imaginit.

 

Thank you for your attention.

0 Likes

awatt
Advocate
Advocate

I've created an autodesk case: Case number23012066

 

I have made some progress. In a test case I renamed the Vault Workspace folder and created a new one. After downloading some older model versions the sync seems to function correctly.
That would solve the problem but I have 20 users who are afraid of losing data and likely many of their workspaces contain the same gremlin. Are there any techniques to hunt down the problem?

0 Likes

ihayesjr
Community Manager
Community Manager

@awatt 

They shouldn't lose data if you move the workspace location. The question is, is their working folder set up correctly?

Is it pointing to the correct location on the drive?

 




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes

awatt
Advocate
Advocate
Accepted solution

Additional hard-won progress.

 

A while ago I created a folder in the workspace for a special project and only gave select engineers access. The project ended and its folder has been largely forgotten.

Because we swap computers among our users some computers had folders and files on the workspace that the users weren't entitled to.

When the workspace sync sees that, it stops dead in its tracks and plays dumb.

That's why the additional permissions let the sync go through.
I can remove the extra permissions now.

So in this instance, I know which folders I can delete or relocate.

It would be nice if the sync could ignore these files / folders instead of giving the false impression that nothing on the drive can be synced.

0 Likes

awatt
Advocate
Advocate
Accepted solution

To add the final detail, the machines that had this problem used Junctions to put the workspace on a drive with more room. It worked fine for a while . . .

 

When I replaced the junction with a standard folder, things worked as advertised.

 

 

 

0 Likes