Account, team and site settings

Two levels of configuration: your account, which covers billing, team and preferences, and each site, which covers what we scan and where we publish.

What can I change in account settings?

At /account, in seven sections.

Section	Covers
Profile	Name, email, and password. Minimum 12 characters; if you signed up with Google you can set a password here without knowing an old one.
Plan and billing	Your plan, credit balance, top-ups and invoices. Billing is self-serve through Stripe's customer portal.
Team	Invite people and set a role.
Notifications	Three toggles: weekly digest, alert emails, product emails.
Sites	Every site on the account, and where to add another.
Beta features	Opt into features still being finished. Today that is Reporting, which reveals Report Studio in the sidebar.
Danger zone	Delete the account.

What can each team role do?

There are four roles. Only the owner can add or remove people; admin, analyst and viewer differ in how much they can change.

Role	Can
Owner	Everything, including adding and removing people. Only the owner can change the team.
Admin	Manage sites, scans and content.
Analyst	Run scans and work with the output.
Viewer	Read only.

How do I delete my account?

Deletion is a 30-day soft delete, and it is cancellable for the whole of that window. Nothing is destroyed on the day you click it. You can also export everything first — Account → Profile → Export returns your data as JSON.

What can I change per site?

At /sites/:id/settings, in five tabs. These are per site, so a change to one site never affects another.

Tab	Covers
Business profile	What the business is, what it sells, and its Google Business Profile URL. This is what grounds prompt generation and content drafting, so it is worth getting right.
Regions	Which markets to scan. The first region is the primary one; free scans cover the primary region only.
Scanning	Scan frequency and scope.
Integrations	Search and analytics connections, publishing channels, and an outbound CMS webhook.
Advanced	Danger zone for the site.

What spends credits?

AI work spends credits: scans across engines, content drafts, agent runs. Your plan includes an allowance and you can top up. Reads never spend credits — only work that calls a model does. This is also why API keys separate read: scopes from run: scopes, so an automation cannot spend credits it was never meant to touch.