Skip to content
PowerOps

Digital agency & media buying

Every client in a workspace of its own

The profiles, proxies and stored sessions that belong to a client stay inside that client's workspace, and a member sees the workspaces you granted them and no others.

PowerOps · Groups
Search
All profilesClient AClient BInternal
Group
Paid social
Creators
Community
Research

An agency's real problem is not running several ad accounts. It is that a client's accounts, routes and sessions have to stay with that client — through a new hire, a contractor, a departure, and an audit six months later asking who had access to what.

A workspace per client

Each workspace holds its own profiles, proxies and synced catalogue, and profile storage is partitioned by workspace on disk rather than only in the interface. A member sees the workspaces you granted them and has no route to the others.

Onboarding is granting access

Invite by email with a role — owner, admin or editor — per workspace. Credentials live with the profile and are never returned by a query, so handing an account to a new person is granting access rather than sending a password. When somebody leaves, revoking membership closes their access everywhere at once, and a password they never saw does not need rotating.

Media buying, specifically

  • An ad account opens from the environment and network it was set up in, by default
  • A client's profiles move between workspaces as a recorded transfer with a history
  • Groups per platform inside a client's workspace, opened together for a working session
  • On the paid plans, Cloud Sync puts the same environment on a second machine

Set this up in a couple of minutes

Download the Windows build, create your first profile, and give one account an environment of its own.