Project Locations
Locations are shared org assets — one warehouse or stage reused across shoots. On a project, the Project Locations tab shows which of those places are linked to this job, with project-specific alias, notes, and optional budget.
Managing the shared catalog (search, archive, org-wide edits) belongs in Locations Library under Organization Hub.
Link vs library
| Locations Library (Org Hub) | Project Locations | |
|---|---|---|
| What it is | Full org catalog | Links to that catalog for this project |
| Typical fields | Name, address, notes, image | Display name (alias), production notes, location budget |
| Who manages | Org Admins | Project or org Admins link / edit links |
Editing the underlying Location address updates it everywhere that Location is used. Alias and project notes stay on the link.
Adding a location to a project
From Project Locations → + Link Location:
- Link from Library — pick an existing org Location
- Create New Library Location — create in the library and link in one step (org Admin only for the create side)
You can set an alias and notes when linking. There is no limit on how many projects share one Location, but each project links it at most once.
Budgets and spend
Each project location can have a location budget. Spend comes from purchases tied to that location on this project. Unset budget means no cap shown; an explicit zero is still a budget. More on budgets: Budgets.
Purchases and scenes
When logging a purchase, the location picker only lists locations already linked to the project — link first if you need a new place. Location detail can also show related scenes and purchases/items.
Who can edit
Viewing uses location view access. Linking, unlinking, and editing alias/notes/budget needs project Admin or org Admin. Creating a brand-new library location from the link modal needs org Admin.