Since only one user is experiencing this behavior, verify that the user has the proper read and write access to the workspace. To test this have another user to sigh in who is not experiencing this behavior, if the other user do not experience the same behavior than it could be that the user who is experiencing the issue should have his/hers credentials evaluated or revised to verify it's administrator read/write access to the workspace on the network.
↧