Clicky User Management — Site Sharing, Guest Access &

Clicky Permission Model

Clicky uses a site-based sharing model rather than organization-level roles. Each tracked site in your Clicky account has its own access list. Users are granted access to specific sites, and their permissions are configured per site. There is no global "organization admin" role -- access is always scoped to individual sites.

The account owner (whoever created the Clicky account) has full control over all sites and can share access with other Clicky users or create guest access links for non-account holders.

Two access mechanisms exist:

1. Shared access -- another Clicky user (with their own account) is granted access to your site. They see it in their own Clicky dashboard alongside their own sites.
2. Guest access (Site Sharing URL) -- a public or password-protected URL that lets anyone view analytics for a site without a Clicky account. Used for clients, stakeholders, or embedded dashboards.

Access Levels for Shared Users

When sharing a site with another Clicky user, you assign one of these levels:

Level-specific behaviors:

• Administrator gives the shared user the same capabilities as the site owner for that specific site. They can modify tracking preferences, manage goals and alerts, and share access with additional users. They cannot delete the site or access other sites in the owner's account.
• User is the standard level for team members who need to monitor analytics. They can navigate all reports, drill into visitor sessions, view heatmaps (if enabled), and use the dashboard. They cannot change any site configuration.
• View Only provides restricted reporting access. The site owner can configure exactly which reports and data View Only users can see. This is useful for clients who should see traffic trends but not detailed visitor data.

Admin UI Paths

Sharing a site with another Clicky user:

Clicky dashboard (clicky.com)
  > Preferences (top-right gear icon)
    > Site Settings (for the specific site)
      > Sharing section
        > Enter Clicky username or email
          > Select access level (Administrator / User / View Only)
            > Save

Creating a guest access link:

Preferences
  > Site Settings
    > Public Access / Site Sharing URL section
      > Enable guest access
        > Optionally set password protection
          > Copy the generated URL

Viewing who has access to a site:

Preferences
  > Site Settings
    > Sharing section
      > Lists all shared users with their access level

Managing multiple sites:

Clicky dashboard
  > Site dropdown (top-left)
    > Lists all sites you own or have shared access to
    > Each site's sharing is managed independently

API Key Management

Clicky provides API access through site keys and site IDs, not OAuth tokens.

• Site Key -- a secret key unique to each site. Found in Preferences > Site Settings > Site Info. Anyone with the site key can query the Clicky API for that site's data.
• Site ID -- the public site identifier used in the tracking code and API requests. Not secret.
• API access control -- there is no granular API permission system. If a user has the site key, they have full read access to all data for that site via the API. Write operations (goal management, visitor annotation) also require the site key.
• Resetting the site key -- if a site key is compromised or a team member with API access leaves, generate a new site key in Site Settings. This invalidates the old key immediately and breaks any integrations using it.

API access implications:

• Shared users with Administrator level can view the site key and use the API.
• Shared users with User or View Only level cannot see the site key in the UI, but if they were previously given the key (e.g., for an integration), they retain API access until the key is rotated.
• Guest access links do not provide API access.

Analytics-Specific Permissions

How Clicky access levels affect analytics features:

• Real-time visitor tracking -- all shared access levels can view the real-time visitor list. View Only users see it filtered based on the owner's configuration.
• Heatmaps -- heatmap data is visible to Administrator and User levels. Heatmap recording configuration (which pages to track) requires Administrator.
• Goals and funnels -- creating or modifying goals requires Administrator level. User and View Only can see goal completion data in reports.
• Custom tracking -- setting up custom data tracking (revenue, campaign parameters, split tests) requires Administrator access to modify the tracking code.
• Alerts -- email alerts for traffic spikes, downtime, or goal completions can be configured by Administrators. Each shared user can set up their own alerts at whatever level they have access.
• Data export -- CSV export from the UI is available to Administrator and User levels. View Only users cannot export. API export requires the site key.
• Visitor session playback -- if session recording is enabled (Pro plan), Administrator and User levels can replay visitor sessions. View Only cannot.

White-Label and Agency Features

Clicky Pro accounts have additional sharing capabilities:

• White-label dashboards -- remove Clicky branding from guest access links. Useful for agencies sharing analytics with clients under their own brand.
• Multiple site management -- Pro accounts can track multiple sites. Each site has independent sharing settings.
• Sub-accounts -- some agencies create separate Clicky accounts per client for complete isolation, then manage them through a parent account arrangement.

Account vs. Site Distinction

An important nuance in Clicky: the account is the billing entity, and sites are the tracked properties. Access sharing happens at the site level, not the account level.

• Deleting a shared user from one site does not affect their access to other sites.
• A shared user cannot see other sites in the owner's account unless explicitly shared.
• The account owner's billing information is only visible to the owner (and Administrators on specific sites with billing visibility enabled).

Step-by-Step Guides

• Add User Access -- share site access with team members or create guest links
• Update Access -- change access levels or modify guest link settings
• Remove Access -- revoke shared access, disable guest links, and rotate API keys