Group access: your whole agency, without the invitation dance

An agency customer told us their onboarding was absurd. Every new colleague had to be invited to every client site, one at a time. With twenty client sites and a handful of new hires a year, that's hundreds of small administrative acts, each one a chance to forget somebody. And when a colleague left, nobody could say with confidence which sites they still had access to.

They were right. That is absurd. Group access is live in production now, and it fixes it.

How it works

Your agency registers its email domains with us. From then on, anyone with an address on one of those domains becomes a member of your agency group the first time they log in, and sees your whole portfolio: your Standard site and the client sites in it. Nobody has to click anything, and no client has to approve each colleague individually.

Departures are one action instead of twenty. When a colleague leaves, exclude them on the group page and their view of the portfolio is gone immediately, rather than surviving in twenty separate permissions that nobody remembers to revoke. An account that ends up with no access at all is deleted within six months anyway, as data protection requires.

Tell us your domains and which sites belong in the portfolio, and we set that up with you, the same way we set up the Agency tier itself. From there your team manages itself.

What an agency administrator controls

One page, Agency group in the dashboard, holds the levers:

Your clients can see you

This is the part we'd ask you to read even if you skip the rest.

Group access is not a back door. Every client can open Users for their website and see exactly who has access, and the list says plainly who is there through an agency and which agency it is. Each individual permission also records who granted it and when, so the question why does this person have access? has an answer six months later.

We built it that way deliberately. An agency that looks after a client's website has a legitimate need to be in there, and the client has a legitimate right to know who's looking. Both are served by the same list. If you're a client reading this and you see an organisation you don't recognise, talk to whoever owns the web internally first, and then to support@webperf.cloud.

Two boundaries worth knowing

Test credits belong to the website, not to the person. Everyone with access to a site draws from that site's allowance, agency and client alike. So agree with each other before somebody orders a 250-page audit on a Starter site. The remaining balance is shown under Tools on every site.

Access is not support. Being invited into a client's account doesn't entitle your agency to ask us questions on that account; the included support belongs to the account's main user. If your agency wants to be able to raise its own questions, that comes with a plan of your own. Answers we give a client are theirs to pass on to you, of course.

Ask us for things

This feature exists because a customer described a daily annoyance instead of quietly putting up with it. That's worth saying out loud: no Webperf Cloud customer should hold back from suggesting a feature. You don't need a business case, a specification, or a sense that your request is important enough. You don't need to be a large account. If something in the service makes your week harder than it should be, tell us. Some requests turn into work we ship in weeks, some turn into a conversation about a better way round the problem, and some are things we've been meaning to do and needed someone to ask for. All three outcomes are better than silence.

Email hello@webperf.cloud with the awkward thing you've been working around. It's how this got built.


Managing a portfolio and want group access set up for your team? Write to hello@webperf.cloud and we'll sort your domains and your slots.