Skip to content
Start free Sign in

Cookie consent for agencies and teams

Every client site, one account.

Kukie.io keeps every client site in one organisation, gives each team member a role and can limit a client to their own site. Nobody shares a password, and a client never sees another client's site.

Start free (opens in a new tab) See pricing

Why it matters

Consent for clients is an access problem.

The technical work is much the same on the 40th site as on the first. What changes is who may touch which site, what a client may see and what happens to a year of consent records when the work ends.

  • Shared password

    One sign-in that everybody uses

    A shared account is the fastest thing to set up and the hardest to unwind. A leaver keeps working access until somebody changes the password, and a client cannot see their own consent data without seeing everyone else's.

  • Retyped by hand

    The house style rebuilt every time

    You settle on wording you can defend, a layout that suits your clients' sites and region rules that match where they trade. Then somebody retypes it on the next site, gets one field wrong, and 2 clients get different consent behaviour that nobody chose.

  • No exit plan

    No plan for the day a client leaves

    Contracts end. If a client's consent history exists only inside your account, they either lose it or you keep holding data about their visitors long after the work stopped. Few people think about it when they set things up.

None of this is unique to agencies. An in-house lead with 12 brand sites, or a freelancer with a handful of retainers, has the same problem at a different scale. The business case for taking it seriously is easier to make once you can show a client what their own site loads.

Access

Two kinds of access, kept apart.

Who is on your team and who may open one site are different questions, and the answer is rarely the same person. Kukie.io gives each its own kind of access.

Your side

A team member in the organisation.

A colleague is invited by email, accepts and works across the organisation as its Owner, an Admin or an Editor. The role applies to every site, so you set it once rather than per client.

Use it for the people who need the whole account in their head: whoever runs delivery, whoever picks up a site when its usual lead is away, whoever answers when a client asks about a banner.

Their side

Access to one site.

You invite somebody by email to one site, as its Admin or Editor, and that is all they get. They see that site and nothing else: not the other clients, not the site list, not your team.

It is how a client's marketing manager reads their own consent rates, and how a contractor fixes one banner during a project. It is also a clear answer when a client asks whether anyone else can see their data.

Both start the same way: you enter an email address and Kukie.io sends an invitation. Nobody has to be a customer already, and nobody shares a password. Each person you invite from outside the organisation takes a team member seat on your plan, and seats beyond your own come with the Pro, Agency and Unlimited plans. Somebody who belongs to more than one organisation, such as your own and a client's, switches between them from the organisation switcher at the top of the dashboard.

Roles

What each role can do.

The dividing line is not seniority but reversibility. An Editor does the day-to-day consent work on a site and cannot do the things that would be painful to undo.

What each Kukie.io organisation role and each kind of site access allows
What you can do Owner Admin Editor Site admin Site editor
Edit the banner, its wording and its appearance Yes Yes Yes On their sites On their sites
Run a cookie scan and categorise the results Yes Yes Yes On their sites On their sites
Read the consent log and consent analytics Yes Yes Yes On their sites On their sites
Generate and publish cookie and privacy policies Yes Yes Yes On their sites On their sites
Export the consent log and analytics as CSV Yes Yes No No No
See every site in the organisation Yes Yes Yes, except sites limited to named people No, only their sites No, only their sites
Give people access to a site and change their site role Yes Yes No On their sites No
Add a new site to the organisation Yes Yes No No No
Invite and remove team members Yes Yes No No No
Change a team member's role Yes No No No No
Delete a site and everything attached to it Yes Yes No No No
Transfer a site to another organisation Yes No No No No
Billing, plan changes and cancellation Yes No No No No

Owner, Admin and Editor are organisation roles. Site admin and Site editor are given one site at a time, by email, and a site admin can invite other people to that site. Somebody from outside your organisation appears on the Team page as a site guest.

Editor is the role most of a team should have: everything needed to keep a client's consent setup correct and published, with the destructive actions out of reach. The cookie scanner and consent records pages cover what those jobs involve.

House style

One setup, pasted onto 20 sites.

Set up one site the way you want every site to look, then copy its settings and paste them onto another site or onto a whole selection at once.

Your house style becomes something you keep rather than something you remember. The wording your lawyer has read, the layout that suits your clients' sites and the region rules for the markets they sell into are decided once, applied everywhere and corrected everywhere when you improve them.

A new client site then matches the rest in the time it takes to paste, rather than a day of setup. One paste can reach up to 200 sites, and if the receiving organisation's plan allows fewer region rules than you copied, the extra rules are skipped and you are told which. Copying settings between sites is included on the Unlimited plan.

Stays with each site
  • Its own cookies, categories and scan results, which are facts about that site
  • Its cookie policy and privacy policy, written around its own cookies
  • Its consent records, which belong to its own visitors
  • Its Google Tag Manager container and Matomo settings
  • Its access list, so pasting settings never gives anyone access

When a client leaves

Hand a site back with its history.

A site can be transferred out of your organisation into the client's own Kukie.io account, consent records and all, so its history stays with the business it belongs to.

  1. Step 1: You start the transfer

    Only the organisation owner can do this, because giving a site away is the one action here you cannot undo. You enter the email address of the person who should receive it, and the request stays open for 7 days.

  2. Step 2: They accept it

    The recipient signs in and chooses which of their own organisations receives the site. They can also decline, and you can cancel while it is pending. Until somebody accepts, nothing moves.

  3. Step 3: The whole site moves

    Banner configuration, region rules, cookies, scan results, legal documents and the consent log all go with it, and the banner on the website keeps working. The access you gave people on that site ends there.

Deleting instead

Deleting the site loses the record

The consent log records which visitor agreed to what, and when, and it is the first thing anybody asks for if a complaint arrives. Delete the site and that record goes with it. Transfer it and the history is theirs, in their own account, under their own billing.

The same move works the other way when you take on a client whose setup is worth keeping. If the site was connected to the WordPress plugin, the new owner generates a new API key after the move.

The whole organisation

Hand over the organisation itself

When the account should change hands as a whole, at a sale or when a client takes over the organisation you built for them, the owner can transfer ownership to an existing team member after confirming their password.

The previous owner stays on as an Admin, every site stays where it is, and on a paid plan the new owner adds their own payment method.

Who it is for

Built for people who run many sites.

If you look after one website and nobody else touches it, a single site on a single sign-in is all you need. These are the situations this part of Kukie.io is built for.

  • A digital agency with a client list

    Consent for clients becomes a service you sell rather than a favour you keep doing: one dashboard, one house style, access for each client and a clean way to hand a site back.

  • A freelancer with retainers

    You look after consent for several businesses at once. What matters most is not repeating yourself: every client site in one place, set up the way the last 5 were.

  • An in-house lead with many sites

    Brand sites, campaign sites, a shop, a careers site and a help centre, each with a team that wants to change something. Most of those people need Editor, and the rest need access to one site.

  • Any team where more than one person publishes

    Once a second person can change the banner, you need to control who can change it and take that ability away again. That is an account question, not a banner question.

    Learn more about account security

How many sites an organisation can hold depends on the plan, and removing the Kukie.io branding from the banner is included on the Agency and Unlimited plans. To see the platform against a real site first, run a client's domain through the cookie scanner, or contact us if your setup looks like none of these.

Questions about agencies and teams

Can I manage cookie consent for multiple websites from one account?
Yes. Every site you add lives inside an organisation, and one dashboard covers all of them. The banner, the scans, the consent records and the legal documents for each site are reached from the same place with the same sign-in, not one account per client. How many sites an organisation can hold depends on the plan, which the pricing page sets out.
How do I give a client access to only their own site?
Invite them by email to that one site, as its Admin or Editor, in Site Settings under Access management. They see the site they were invited to and nothing else in the organisation, so a client can look at their own consent records and their own banner without seeing the rest of your client list. Each person you invite from outside the organisation takes a team member seat on your plan.
What is the difference between an organisation role and site access?
An organisation role applies across the whole organisation. The Owner has full access, an Admin can manage sites and invite people, and an Editor can work on the banner, scans, consent log and legal documents but cannot delete a site or its consent records, or export them. Site access is given one site at a time instead, as Admin or Editor of that site, and it is the right choice for a client or an outside collaborator who should never see the other sites.
What happens to a client's consent records when they leave the agency?
Transfer the site to their own organisation rather than deleting it. The site moves across with its consent history, banner configuration, scan results and legal documents, so the client keeps the record of what their visitors agreed to and when. Deleting the site instead would delete the evidence they might later be asked to produce.
Can I remove the Kukie.io branding from client banners?
Yes, on the Agency and Unlimited plans. It is a setting on each site's banner, so you can leave the branding in place where nobody minds and remove it for the clients who would rather it were not there.
Do I need a separate Kukie.io account for each client?
No. One sign-in, one organisation and every client site inside it is the usual arrangement. A separate organisation is worth creating when the billing has to be separate, because each organisation carries its own plan and its own list of team members. Most agencies run one organisation and use site access to keep clients apart.

Run every client site from one dashboard.

Add your first client site and set up its banner. The pricing page shows how many sites and team members each plan includes.

Start free (opens in a new tab) See pricing

Related features

Running consent for other people raises questions about records, access and evidence. These are the pages that answer them.

See all features

More on running consent at scale

Practical reading on managing many sites, talking to clients and choosing a platform.

See all articles

Disclaimer

Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.

Listed on

Kukie.io on Trustpilot (opens in a new tab) Kukie.io on G2 (opens in a new tab) Kukie.io on SaaSHub (opens in a new tab) Kukie.io on AlternativeTo (opens in a new tab)