Read-only object status is a property of the local cache, whether the workspace is online, offline, or portable. There is no notion of a locked object in the server-side workspace (which is viewed in standalone browser) or the commonspace.

When you update a locked object in workspace, the lock is retained even though a new version is created to the workspace. This is useful when you are not the owner of the CAD docs or cannot modify it. For example, your colleague is the working on part, abc.prt. This morning you added it to your workspace and either explicitly or automatically locked it, since you don’t want to change it. Now your colleague checks in a new version and you want to get it; but it still doesn’t change the fact that you can’t or shouldn’t modify abc.prt. The update action will now bring that new version and lock it so you can get your updates and keep it read only at the same time.

If a config.pro option such as regenerate_read_only_objects is set to true in aCreo Parametric session, the modification of locked objects is allowed during regeneration. The objects remain read-only, but are marked as modified.