Why is the editor read-only?
When a scene opens read-only, a line under the header says why. There are four reasons, and the seat is the one that surprises people.
- *View only: editing needs a collab seat in this organisation.*
- You have no collab seat. This applies to admins too. An administrator can give you one on the Members screen. See Collab seats and roles
- *This scene is locked.*
- An administrator locked the scene. It stays read-only for everybody until it is unlocked
- *View only: you are a guest on this project.*
- You reach this project as a guest. Guests look, and never edit
- *View only: your role on this project is viewer.*
- Your role on this project is viewer, through the organisation or an override. See Who can reach a project
A read-only editor shows the same plan, with everything that writes removed: no library to place from, no imports, no project settings, no version marking. That is deliberate: the plan is meant to be looked at in the same view it was built in. Comments still work; see Comments.
Locking a scene
Administrators lock and unlock a scene in the Explorer, beside the scene list. A locked scene is marked locked in the list.
Nobody can edit or delete it until an administrator unlocks it.
Its area and description can still be changed.
Releasing a version locks the scene (Release a version).
When live editing is on, locking reaches every open tab within seconds: the scene turns read-only for everyone in it, and unlocking makes it editable again without a reload.