Hello,
When a project (workspace) is already opened by an user, other people cannot access before the first person has left. Can the project maintainer change this behavior somewhere? Otherwise, it’s quite embassing for us in practice.
Thank you in advance.
Best regards,
Huy
Hi @vuquochuy ,
If I understand you correctly, you are referring to the feature that locks the user interface for other users when one user is already in that entity? This feature is there to ensure that input can only be changed and saved by one user at a time.
We did notice that some tree apps have been designed such that the root entity acts more as a dashboard or landing page for users, which do not require saving. For this case, a feature has been rolled out a couple of months ago to accommodate for this scenario:
Maybe this is what you are looking for?
Hi @mslootweg,
For the entity, this feature is interesting for us as we do not want several people can simultaneously make changes on the same entity. I’m actually talking about the workspace. Recently a user’s made some changes within an entity and sent notification to another person. This latter wanted to access the workspace where the entity is located but the workspace is blocked, meaning he could access the workspace but couldn’t do anything, a message is displayed saying the workspace remained opened by the other user. So the first user had to get out of the workspace before the second one could access his turn.
Could you have a look at this?
Thanks.
Best regards,
Huy
The locking of the entity is there to ensure that no unexpected changes occur while the one person is busy working in that entity. But I understand your case (I’ve experienced this myself countless times) where the other person does not work in the entity anymore, but forgot to exit that entity.
@tvantil FYI.