Organise a project’s documents and canvases
Use a project to hold one outcome and its resources. Give documents and canvases distinct jobs, use folders where they clarify the structure, and test that the resource tree remains understandable after a rename, move or recovery. Follow the controls that are available for your account.
Open sidebar → Select project → Library → Create resourceWhat you’ll learn
- Create the right resource for its purpose.
- Rename and arrange a readable project tree.
- Understand tree locking, Trash and Restore.
Captured in Boilerrum with an illustrative project. The app interface is shown in English.
In this guide
01
Choose the project before adding resources
Read the workspace name, open Select project and choose the project that owns this outcome. If a new project is needed and New Project is available, enter Project name and choose Create project. Check the selected name after the dialog closes. Library displays the active project’s resources, so a familiar document name alone is not enough to identify the correct project context.
02
Give each resource a clear job
Open Create resource beside Library. New Folder organises related resources, New Document holds written context, and New Canvas provides a visual working surface. Start with only the resources the outcome needs. A document opens on a canvas and may cause a host canvas to be created if none exists; this is why the first document can add more than one library entry.
03
Name resources and add useful children
Use a resource row’s actions → Rename to replace an untitled name with a recognisable purpose. Press Enter to save or Escape to cancel the inline edit. Expand a folder and use Add child resource to choose an allowed child type. Available options depend on the parent and your permissions. Open each new item and check its name and placement before adding another level.
04
Arrange the tree and understand the lock
When moving is permitted, drag a row before or after a sibling to reorder it, or inside a compatible container to nest it. Watch the drop indicator and verify the resulting parent after release. The tree rejects moves into an item’s own descendants. Lock resource tree prevents accidental local rearrangement; Unlock resource tree restores those controls but does not grant server write permission.
05
Use Trash deliberately and verify recovery
Before using a row’s Delete action, inspect the selected item and its children. In the managed live library, Delete moves the resource into Trash. Expand Trash and choose Restore on the intended item when recovery is needed. Reopen it and confirm its contents and position. If the tree reports a save or permission error, read it and retry through the visible controls before repeating the operation.
A project library with named resources, understandable nesting and a verified recovery route.