Team, Roles and Workspaces

Invite your team, choose what each person can do, and decide which workspaces they see.

An account can hold many workspaces, one per website, and one team. Each person on the team has a role, which sets what they can do, and an access level, which sets which workspaces they see.

Roles

RoleWhat they can do
OwnerFull control of the account, its team, billing and every workspace. The owner role is never assigned by invitation or role change.
AdminEverything a Member can do, plus manage the team (invite and remove people, change roles and access) and billing. Cannot transfer ownership or delete the account.
Billing ManagerEverything a Member can do, plus manage the payment method, spend cap and invoices. No team management.
MemberUse RankDebug within the workspaces they are given. No billing access.
ViewerRead-only within the workspaces they are given. Cannot connect sources, start checks or crawls, or change anything.

Some workspace settings are narrower still. Crawler access, report share links and editing a workspace are for the workspace owner or an admin, and deleting a workspace is for its owner.

Inviting people

On Team, click Invite, enter one or more email addresses, pick a role and an access level, and send. You can also generate an invite link to hand over yourself. Pending Invites lists the invitations not yet accepted, which can be resent or revoked.

The access level is either All workspaces, which covers every workspace on the account including ones created later, or a chosen list of workspaces, which new workspaces are not added to.

People can be suspended and reactivated, or removed. Every invitation, role change, access change, suspension and removal is recorded in the team's activity.

Workspaces

Settings → Workspaces lists every workspace you belong to with your role in it. A new workspace needs a name and the website it covers. Each workspace's settings hold its name, website and timezone, which sets when email digests go out.

Deleting a workspace deletes everything in it and cannot be undone.

Related documentation
  • Guide

    How the parts of RankDebug fit together, and where to find each one in the dashboard.

  • Connections

    How data sources connect to a workspace, how often they sync, and what happens when you disconnect one.

  • Search Console

    Connect Google Search Console with read-only access. What RankDebug pulls and what it is used for.

  • Google Analytics

    Connect Google Analytics with read-only access to see what search visitors did after they landed.

  • Cloudflare

    Connect Cloudflare with a read-only API token to see which crawlers reach your site and what the edge did to them.

  • Bing Webmaster Tools

    Connect Bing Webmaster Tools with an API key to add Bing search data and crawl statistics.

  • GitHub

    Connect a GitHub repository so production deploys are recorded on their own, with the SEO-relevant files each one changed.

  • GitLab

    Connect a GitLab project with a read-only token so production deploys are recorded on their own.

Was this helpful?

On this page