Note: The client workspace is rolling out gradually, so the controls for it may not be enabled for your team yet. If you don't see them, check with your account lead before promising a client access.
Their own front door
Each client workspace lives at its own address — your Omega address plus the client's short name (for example, omega.novapower.io/bostonproper). Clients sign in through the same login page you use, and the sign-in screen greets them with their brand name. Once inside, they see the familiar Omega look — sidebar and top bar — trimmed to two products: Chat and Scan.
What they can see
Chat with Iris. Iris answers questions about their data only, keeps their conversation history, and speaks to them as "you" and "your business" — never "the client." It delivers insights and the why behind the numbers, but it never prescribes strategy: budget moves and action plans stay with your team, and Iris says so. It ranks evidence carefully (business results over platform-reported numbers), never invents a figure, and flags data gaps plainly.
Their creative performance. Where a brand's paid social and video ads run through nova's Creative Affinity, Iris can show which creatives are performing — with the actual ad thumbnails and videos in the chat, each stamped as Creative Affinity. It works on the brand's own ads only and builds each view on the fly from the client's data: the saved reports, folders and templates your team maintains in nova stay internal, and Iris never links a client into nova itself.
Their signals. The Scan area shows their signal board plus Overview, Coverage, Monitoring, and view-only Metrics. Signal rows are filtered by policy: clients see only open signals, and only performance categories — account-health and data-hygiene findings are held back, because "your tracking is broken" is a conversation for the account team, not a board card. Dismissed and completed history stays internal, and in Monitoring, actions show as taken by "Power Digital," never by a named teammate.
Shared folder. When your account team has linked a client shared folder (see Sharing documents with a client), a compact Shared folder card appears on the Settings tab of their Preferences, below Integrations, naming that one Google Drive folder, with a single Open in Google Drive button. The folder opens in Drive under the client's own Google account, so Drive's sharing decides what they can actually open; Omega never lists or shows the contents. Iris can read that folder in their chat — it lists the files and reads a document's text when a client asks about it, naming the file — and nothing else in Drive.
Files and preferences. Under their profile menu, clients can set personal chat preferences, view read-only client settings (company info, standing instructions, calendars, connected integrations), and upload files that become context for their account.
What they can do
Ask questions. Iris closes most analytical answers with one question about their business — a launch, a promotion, a goal shift. What clients share back is captured as business context your team can build on.
Comment on signals. A client's comment lands in the same discussion thread your team uses, clearly labeled as coming from the client, and your team is notified. It's one-way by design: clients can write into the thread but never read it back, so internal candor stays internal.
Request data corrections. In Chat, a client can flag a number they believe is wrong, provide the correct value, and cite their source. Client corrections never change anything on their own — they land in a review queue for your account team to approve or decline.
Share a chat. From the share button in a chat's header, or Share in the chat's menu in the rail, a client copies one link that opens the chat for two audiences: their own team (anyone on their account who has access to that chat's brand, signed in) and their Power Digital team (anyone at Power Digital, signed in). Copying the link turns on both, and each has its own toggle, so the client can switch either one off. A staff member who opens the client's link lands on the internal thread; one who isn't signed in to Omega gets a Sign in with Google option on the client's sign-in page that takes them straight there. Readers see everything in the chat — attached files, reports, charts and dashboards, and creative images — but it's view-only: only the person who started the chat can send messages or change who it's shared with. Turning a toggle off stops the chat and its files opening for that audience at once (removing a seat, or that brand from a seat, does the same), though a chart, deck or file a reader already had open may stay viewable for up to an hour in Omega.
What they never see
Clients never see other clients' data — each workspace is walled to one client, with no client picker. They also never see internal surfaces: Agents, Plan, Flight, the Workflow board, internal discussion threads, review queues, or unreviewed work. If it isn't finished and client-ready, it isn't in their workspace.
Tip: Before a client meeting, skim their signal board yourself — what they see is a subset of what you see, so know which signals are visible on their side.