How to use Orbit /
A practical path through Orbit, from the first input to a saved, reviewable result.
A plum review room puts the artwork at the centre, with a project-file rail, version history, numbered pins and threaded feedback. The public interface is an interactive example of a full-stack creative-review app.
Before you begin
Explore the public interface with example records first. Its preview interactions stay in the current view; use the workspace link to open the account-backed product described below.
Create an account in Orbit and work in its own private workspace. Accounts and records from another Lumia product are separate. Small creative teams, independent producers and internal reviewers who need a clear decision record for visual work without managing feedback across several conversations.
Follow the workflow below to understand the application. Contact Lumia for a guided walkthrough; account access is private. An exported file reflects the record at the time of export.
Create a room around one decision
Give the room a title that explains what needs review, then upload the media you own or are authorised to share. The uploaded file becomes the first version. Check that the actual image renders before adding feedback. Keep distinct deliverables in separate rooms so a decision has an understandable scope.
Put feedback where it belongs
Select a point on the image and write a specific note about that location. The pin provides spatial context; the note explains the change or question. Resolve notes as the work is reviewed. Earlier notes remain associated with their original version, helping a reviewer distinguish completed work from a current concern.
Approve the current revision
Review all open notes for the current file before recording approval. Orbit blocks sign-off while those notes remain unresolved. Uploading another version clears the previous approval and returns the room to review. Download the decision log when the team needs a portable record of versions, feedback and the recorded decision.
Share a bounded view
An owner can create an expiring review link for a limited view of the room. That link provides reading access to the room’s media and review record. It does not give the recipient ownership of the workspace or permission to approve work. Use a signed-in authorised workflow when a decision must be recorded.
Operating the product
Start with the public interface to explore the design using example records. These interactions stay in the current view. Open the private workspace from the interface to use the existing account, storage and product workflows.
When a file upload fails, keep the previous version and review state. Correct the file or size issue before retrying.
When the saved version changes during review, reload and inspect the current file before approving again.
Use the decision-log export for a portable review record; retain the original media separately when needed.
Treat review-link access as reading access. Record approvals through the authorised workspace.
A deployment handover must verify configured origin, persistent records and files, backup recovery and notification providers independently.
A similar problem in your business?
Bring a real workflow, representative inputs and the result that needs to be reliable.
Shape a project brief