Skip to main content

Account & Workspace Basics

Understand how accounts and workspaces are structured in Keyword.com and how data is organized across teams.

Updated over 3 weeks ago

What it is

Keyword.com has two distinct work areas in a single app:

  • Google SERP Tracker

  • AI Visibility Tracker

Shared settings (users, access, billing, subscription) work across both, but feature settings are isolated per tracker.


How the app is structured

Shared across the app:

  • User identity & login

  • Team access & permissions

  • Billing & subscription

  • Organization settings


Separate work areas

1. Google SERP tracker

  • Keyword Ranking Table (Google SERP keywords)

  • SERP-specific settings (alerts, Project currency, Date Format, PDF schedules)

  • Google integrations

  • SERP dashboards

  • ViewKey branding

  • API


2. AI Visibility tracker

  • AI visibility keyword lists

  • Prompt settings & AI sources

  • AI dashboards & trends


Subscriptions

Users can subscribe independently to:

  • Google SERP Tracker

  • AI Visibility Tracker

Each subscription can be active on its own or together.


User & access permissions

Keyword.com supports role-based access and shared access so you don’t have to share credentials.

How shared access works

  • You invite users by email and assign permissions.


Permission types (explained)

Permission

What it allows

View Only

Can see data but cannot edit anything.

Add-on User

Standard user: view & edit categories/projects they have access to.

Admin Access

Full control: modify settings, manage users & access, and perform all edits.


Quick steps to add a user

  1. Go to Settings > Shared Access

  2. Click + New User

  3. Enter email, temporary password, choose permission level and project limitations

  4. Click Save

💡 Note: Shared users do not share your login credentials.

If an email is already associated with a Keyword.com account, the system handles authentication without duplication.


Best practices

  • Give View Only to stakeholders who need visibility but shouldn’t change configs.

  • Use Add-on Users for team members who manage keywords and alerts.

  • Reserve Admin Access for workspace owners or operational leads.

  • Review access regularly, especially when people leave or change roles.

Did this answer your question?