Members and roles

Invite people to your team, understand what each of the four roles can do, and control which projects a member can see.

Access in Clakta has two layers. Team roles decide what someone can do in general; project membership decides which projects they can do it in.

Inviting people

Go to Team settings → Members and send an invite by email. The recipient gets a link, creates a Clakta account if they do not have one, and joins with the role you assigned.

Your plan caps how many members a team can have — 1 on Free, 3 on Pro, 10 on Business. See Plans and limits.

The four roles

Owner

Full control. Everything below, plus the things only owners can do:

Create, update and delete projects
Update team settings and delete the team
Create, update and delete API keys
Manage billing and members

Keep at least two owners. A team whose only owner loses access needs support to recover.

Member

The day-to-day working role. Members can:

View and edit the dashboard, including presets and widgets
View and update campaigns and ad groups in the Ads Manager
View and manage orders, customers and products
Read analytics
View team and project details
View API keys, but not create or change them
View data streams, but not manage them

Members cannot create or delete projects, change team settings, or manage API keys.

Editor

A narrow, technical role scoped to tracking setup. Editors can view and manage data streams — the scripts that collect events — and nothing else in the permission matrix.

Use it for a developer or agency who needs to configure and troubleshoot the tracking script without seeing your orders, customers or revenue.

Billing

Scoped to billing. Use it for a finance contact who needs invoices and plan management but has no reason to see performance data.

Permission matrix

Capability	Owner	Member	Editor	Billing
Dashboard — read & write	✅	✅	—	—
Ads Manager — read & write	✅	✅	—	—
Orders — read & write	✅	✅	—	—
Customers — read & write	✅	✅	—	—
Products — read & write	✅	✅	—	—
Analytics — read	✅	✅	—	—
Teams — read	✅	✅	—	—
Teams — write	✅	—	—	—
Projects — read	✅	✅	—	—
Projects — write	✅	—	—	—
API keys — read	✅	✅	—	—
API keys — write	✅	—	—	—
Data streams — read	✅	✅	✅	—
Data streams — write	✅	—	✅	—

When someone lacks a permission, Clakta tells them which roles do have it rather than failing silently.

Project membership

Team role is not the whole story. A member also has to be added to a project to see its data.

Manage this in Project settings → Members, or when creating the project. Owners always have access to every project.

This is how you run several clients or brands in one team. Give each person the Member role, then add them only to the projects they work on.

Changing and removing

Change someone's role from the members list at any time; it takes effect immediately. Removing a member revokes their access to every project in the team at once — API keys they created are not automatically deleted, so review those separately when someone leaves.

Review API keys when someone leaves

An API key keeps working after the person who created it is removed. Audit Team settings → API keys as part of offboarding.

API keys

Create scoped keys for programmatic access, authenticate your requests, and keep keys safe once they are issued.

Plans and limits

What each plan includes, which limit you are most likely to hit first, and how to decide when to upgrade.

Usage and billing

Read the usage charts, understand when your allowance resets, and manage your plan, invoices and payment method.