1001 SEO Media
All posts
By 1001 SEO Mediaagency operationsaccess controlreportingGEO

Giving client teams access to AI visibility data

Seat limits used to decide who could see the dashboard. Now that they are gone, here is how we choose roles, keys and audit trails for client stakeholders.

For a long time, access to a client's AI visibility dashboard was a rationing exercise. The platform capped seats, so we chose carefully who got one. The head of marketing, yes. The content lead, probably. The three regional managers who kept asking for numbers, they got a PDF.

That changed on November 4. According to the Promptwatch changelog, team seats are now unlimited on every plan. Contracts that were signed with a custom seat limit keep it. Before the change the caps ran from one seat on the smallest plans to twenty on Enterprise, so for most of our clients this is a real difference.

It is also a risk. When the limit disappears, the only thing standing between a client's dashboard and everyone in their company is your own judgment. Here is the judgment we apply.

Start from what each person needs to do

We ask one question per person: what will this person do with the data? The answer sorts people quickly.

People who decide. Executives and heads of function read trends and sign off on priorities. They need to see, not to change.

People who produce. Content writers, SEO leads, and developers act on findings. Some of them will need to edit prompts, tags, or monitors.

People who account. Finance, legal, and procurement occasionally want one number or one export. They rarely need a login at all.

Most client organisations have many more deciders than producers. That ratio is why the default role matters.

Roles: viewer first

Promptwatch has owner, editor, and viewer roles, with access that can be set per project and with bulk invites for larger groups. We hand out viewer by default and promote on request, with a reason.

Our usual split looks like this. The client's main marketing contact is an owner, because someone on their side should hold the account if our contract ends. Their producers are editors on the projects they work on. Everyone else is a viewer. Project-level access matters when a client has several brands or regions: the German team does not need to browse the UK project, and it avoids the awkward moment where one team sees another team's competitor list.

Bulk invites save the afternoon you would otherwise spend adding thirty email addresses one at a time.

Keys are a separate decision from seats

People often assume that giving someone a seat settles the access question. It does not, because data also leaves through the API and through MCP clients that connect to the platform.

Promptwatch supports scoped API keys at project, organisation, and read-only levels. Our rule is one key per purpose, read-only unless the script has to write. A reporting dashboard that pulls numbers into a client's BI tool has no business holding a key that can delete a monitor. We name each key for its job and its owner, so that when the person leaves we know what to remove.

Unlimited seats do nothing for keys. If anything they raise the number of people who might ask for one.

Audit trail: know what you can and cannot see

When more people can log in, the question "who changed that prompt set" comes up more often. Promptwatch has an audit log that shows whether a change came from the dashboard, the API, an MCP client, or Agent Chat. It is available on Business, Agency Scale, and Enterprise, and it is visible to owners only.

On plans without it, we keep our own record. Every change to a prompt panel, competitor list, or brand definition gets a date and a reason in the client file. It is dull work. It also settles most arguments before they start.

A short onboarding routine for new client users

We do not just send an invite. Each new person gets three things in the first message: what the dashboard is for, which two or three views matter for their job, and who to ask if a number looks strange. Without that, a new viewer opens the heatmap, sees a score they do not understand, and writes to the CEO.

For the producers we add one more rule: if you change a prompt, tell us. Changing the panel mid-quarter breaks comparisons, and the person making the edit usually has no idea.

Review access every quarter

The old seat cap did one useful thing by accident. It forced a cleanup, because someone had to give up a seat for someone else to join. With no cap, accounts for people who have left the client company can sit around for months.

We put an access review in every quarterly meeting. We list who has a seat, who has a key, and who has not logged in recently, and ask the client owner to confirm each one. It takes ten minutes and nobody enjoys it, which is a fair sign it is worth doing.

If you want to see how the roles and keys behave before you decide on a setup, the 7-day free trial on Promptwatch is a reasonable place to try them. If you would rather have us set it up for your team, write to hello@1001seomedia.com.