Skip to main content
The standard agency deliverable is a monthly report. A client login is better: your client signs into OpenLens and watches their own visibility move, on the dashboard you built for them, any day they want. You still control exactly what they see. Client logins are free and unlimited on every plan. They never count against your seats.

​
How to set one up

  1. Open Team in the sidebar.
  2. Enter your client’s email and pick the Client role.
  3. Add the one project they should see (you can add more than one if the engagement covers multiple brands).
  4. Send the invite. On their first sign-in they land in your org with access to exactly that project.

​
What a client sees

Everything read-only on their assigned projects: the dashboard, topic performance, citations, workstreams, and reports, including the PDF download. The numbers they see are the same numbers you see. What they don’t get:
  • No edits, anywhere. They can’t run prompts, change brands or topics, touch the schedule, or alter settings. Read-only is enforced on the server for every write, on every project, even if you accidentally assign them as manager.
  • No other projects. A client assigned to Acme has no way to know Beta exists.
  • No org internals. No Team page, no Usage page, no billing, no org API keys.

​
API and MCP for clients

A client login can create a personal API key and connect over MCP like any other user. Access stays read-only and scoped to their assigned projects, and their calls draw from your org’s monthly API and MCP allowances. Useful when a technical client wants to pull their own numbers into a spreadsheet or ask an agent about their visibility.