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 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.
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.
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.