Folders, sources and access
Source is where an item came from and is immutable. Folder is where you filed it and carries the access rule. A tile can honestly read "unattached" while sitting in a folder: it arrived attached to nothing, and you filed it.
The source axis
Immutable. It records how the item entered the project.
| Source | Where it came from |
|---|---|
| Chat | Attached to a message in crew comms. |
| Errand | Shot against an errand, usually proof of delivery or collection. |
| Scouting | Photos of a scouted item. |
| Location | Shot against a location: recces, parking, access. |
| Unattached | Captured without a target. Still useful, just unlabelled. |
The folder axis, and access
Folders are how you organise, and they’re also how media access is scoped. You see your own department’s folders implicitly, plus anything explicitly granted. The server only sends what you may see, so the rail is navigation rather than a filter over things you could otherwise reach.
Media in no folder stays visible to the whole project. That’s why nothing disappeared when folders arrived, and it’s the thing to know before assuming an unfiled photo is restricted.
What an item stores
| Field | What it holds |
|---|---|
| Type | Photo or video. |
| Caption | Yours to write. The difference between a useful archive and 4,000 files. |
| Captured at | When it was shot rather than when it uploaded, so the grid is in the order things happened. |
| Location | Capture coordinates, when the device provided them. |
| Uploaded by | Which crew member shot it. |
| Dimensions / duration | Size, and length for video. |
| Status | pending, uploaded or failed. A failed upload is visible rather than silently missing. |
cinemasetfree