All guides, by feature
Share a build with a client
Press Share with client on the build in your Library, then approve it in Approvals. Approving files it into the client’s Documents, where their portal users can download it.
Before you start
- Who can do this
- Anyone with a seat can stage a share. Approving it needs an Owner, Admin or Manager.
- You need
- A ready build made for a client. Builds that cover your whole agency have no client to share with.
- Availability
- If enabled for your agency
- Where in Orbit
- Sidebar › Workspace › Mission Control
Steps
Tick a step’s number when it’s done. We’ll remember where you were.
Open Mission Control. In Library, find the build. It shows internal and “Agency only — the client cannot see this yet.”
Press Share with client. The badge changes to .
In Approvals, find the request, which reads “Make … visible to … in their portal”, and check the previews.
Press .
When it worked
The request leaves your Approvals, and the file is in the client’s Documents, where anyone with portal access can download it. The Library marks the build [[shared]].
If something goes wrong
There’s no Share with client button.
It only shows on a ready build made for a client that isn’t already waiting or shared. Builds such as Pacing summary or Renewal risk memo cover your whole agency, so there’s no client to share with.
Orbit showsSending a report to a client needs an admin or manager. Ask one to approve it.
Only an Owner, Admin or Manager can approve sending a report to a client.
Orbit showsThe client can already see this one.
It’s already shared, so there’s nothing more to do.
How it works
Explainer: Ops board jobs and where builds go
Each job on the Ops board builds a document in one tap. Builds land in your Library. A build for a client is also filed in that client’s Documents, where only your agency can see it until you share it.
| Seat | Jobs | Asks for |
|---|---|---|
| Executive | Monthly performance report, Renewal risk memo, Board update | Client and month for the report; month for the board update |
| Account Mgmt | QBR deck, Renewal risk memo, Status roundup | Client and month for the QBR deck |
| Paid Search & Social | Pacing summary | Nothing |
| Programmatic | Pacing summary | Nothing |
| Analytics | Data trust report | Nothing |
| Strategy | None yet | None |
- A build usually takes 2 to 5 minutes. Its badge moves from queued to building to ready or failed. You can leave the page; Orbit notifies you, for example “QBR deck is ready”, or “… needs a look” if its review found issues.
- Period offers single calendar months: this month and the five before it. A monthly build is compared with the same number of days immediately before it, so October is compared with Aug 31 – Sep 30. Both date ranges are printed on it.
- Renewal risk memo, Status roundup, Board update, Pacing summary and Data trust report cover your whole book, so they stay in your Library only.
- The Library shows your 3 most recent builds. Each has a badge: internal (only your agency can see it), awaiting tap (waiting in Approvals) or shared (the client can see it).
- The line under a build, such as Reviewed or Reviewed with issues, shows the result of Orbit’s check of the build. Hover it to read any issues.
- Jobs that are checks or money moves rather than documents aren’t shown. Orbit sets each seat’s jobs; your agency can’t add them.
Explainer: Approvals: what waits for your tap
Anything that would reach a client or someone’s calendar waits in Approvals until you press Approve. Each card says exactly what approving does.
| Request | What Approve does | Who can approve |
|---|---|---|
| Share a report or deck with a client | Files it into the client’s Documents, where anyone with portal access can download it. | Owner, Admin or Manager |
| Schedule a meeting | Creates the event on your calendar and emails an invitation to every attendee. It can’t be un-sent. | The person it was requested for |
| Move a meeting | Moves the event and emails everyone the new time. It can’t be un-sent. | The person it was requested for |
- You see only requests made for you that nobody has decided yet.
- A card can carry a risk label: Moves money or Goes outside Orbit.
- Report requests show page previews and a link to open the file. Meeting requests tag each attendee “free” or “not checked”.
- Reject turns the request down and removes the card.
- A Specialist can’t approve sending a report. Pressing Approve shows “Sending a report to a client needs an admin or manager. Ask one to approve it.”
- Voice can’t approve anything. Every approval needs a tap.