Who can use it, and in which environment
The Media Library is part of the Admin Console and is available only to PlaceNest administrators with content-editing permission. Members of the public never see it — they only see items that have been published and placed on a page.
Each environment (development, test and live) has its OWN Media Library: its own items, files, approvals and history, managed in its own Admin Console. Items uploaded in one environment are never copied to another; a new release of the application changes the application only and never overwrites the library's content.
Uploading and supported formats
Upload single files, several files or a whole folder. Every upload becomes a draft and is checked before it can be used: the file type must match its content, executable or active content is refused, Office files with macros are refused, and photos are re-encoded with location and camera details removed. A file that is already in the library is refused and the existing item is named.
The supported-formats table on the Media library page lists every accepted format with its size limit.
Important: In the test and live environments, older document formats are refused for safety: Rich Text (.rtf) and the legacy Word, Excel and PowerPoint formats (.doc, .xls, .ppt). Save them as PDF, .docx, .xlsx or .pptx first.
Approval with one authenticator code
Nothing becomes public by uploading or editing. Publishing, archiving, restoring, rolling back, scheduling, and publishing or unpublishing a placement all go through a batch: select the items, choose the action, and the batch is frozen — its exact contents are shown on the next page. Approve it with ONE fresh code from your authenticator app. If anything in the batch changed after it was frozen, that item is not carried out and the batch shows why.
- Step 1 of 3: UploadThe file is checked and becomes a draft item.
- Step 2 of 3: Freeze a batchChoose Publish (or another action) for one or more items.
- Step 3 of 3: ApproveReview the frozen batch and enter one authenticator code.
Outcome: Each item in the batch shows its own result. A batch where any item failed is shown as partially completed, never as fully completed.
Scheduling
Publishing or archiving an item, publishing or archiving a gallery, and publishing or unpublishing a placement can be scheduled for a later time. Enter the time as Canberra / Sydney local time — daylight saving is applied automatically and a time that does not exist when clocks go forward is refused. The schedule is approved with one code like any other batch and runs at that time.
- Schedules must be at least one minute and at most a year ahead.
- Pending schedules are listed under Media library → Schedules, where they can be cancelled or cancelled and scheduled again. Cancelling needs no code because it only removes a future action.
- While a placement has a pending schedule it cannot be edited or removed — cancel the schedule first.
- If the item, gallery or placement changes after it was scheduled, the schedule is not carried out and is shown as superseded.
- A placement that follows the published version may be scheduled together with the item's own scheduled publication, as long as the item is scheduled no later than the placement.
Placements and visibility
A placement shows one item on a page or article (for example a help article, the Energy Centre or a calculator). One item can be placed in many places without being copied. A placement either follows the item's published version or stays pinned to the version that was published when it was approved.
An item can be public or for signed-in members only. A members-only file is never served to someone who is not signed in. Making an item more restricted is always allowed; making a members-only item public is possible only while it is a draft, so the change goes through approval again.
Rolling back
Content: roll an item back to an older version, unpublish a placement, or archive an item — each through an approved batch, without a new release. Archiving never deletes the stored file; an archived item can be restored.
Application: if the application itself is rolled back to an older version, the Media Library switches itself off until the application and its database match again — the library pages explain this, and no item is shown or served in the meantime. Older application versions that cannot protect members-only files are refused as rollback targets while members-only items exist.