Documentation
Settings: Integrations, Billing, Team & Projects
Visibilitas keeps organization-wide settings (integrations, billing, and team members) separate from the settings that live inside each individual project. Organization settings apply to everyone in your account, while project-level settings (general details, access, AI usage) only affect that one website.
What you can see and change on these pages depends on your role. Built-in roles are Super Admin, Org Admin, and Member, and an Org Admin can also create custom roles with a hand-picked set of permissions for finer control.
Integrations
The Integrations page is where you connect external data sources at the organization level. Google Search Console and Google Analytics connect through a standard OAuth sign-in flow: click Connect, authorize access in the Google prompt, and you're redirected back with the integration marked Connected. Any other integration your organization uses (connected through its own setup flow elsewhere) also shows up here as a status row that can be disconnected from one place.
Each connection shows a clear status: a green Connected badge, a Not connected state, or an amber Error badge if the last sync failed. Hovering or checking the row gives you the last sync time and, if relevant, the last error message. Disconnecting an integration removes access immediately; you can always reconnect later by running through the OAuth flow again.
This page requires the Manage integrations permission. If you don't have it, you'll see a message explaining that you don't have access instead of the connection list. Ask your Org Admin to connect the integration or to grant you that permission.
Billing & your plan
The Billing page summarizes your organization's current subscription plan: its name, price, billing interval, and the limits that come with it: websites, tracked keywords, AI queries per month, and team members. Visibilitas plans range from Basic through Growth and Scale up to invite-only Enterprise, each unlocking higher limits, faster crawl/SERP schedules, and features like white-label reports and forum/YouTube opportunities on the higher tiers.
Under Switch plan, you can move to any other self-serve plan; choosing a new plan takes you to Stripe Checkout to complete the change. If your organization has an active Stripe customer, an Open billing portal button lets you update your payment method, view past charges, or cancel. All of this is handled securely by Stripe rather than inside Visibilitas itself.
The page also shows your upcoming invoice (amount due and the date it's due) and a table of recent invoices with their status and a link to download the PDF or view the hosted invoice. This page is visible to anyone who can view billing information for the organization.
Team members & roles
The Members page is where you invite new teammates and manage everyone already in your organization. Enter an email address, pick a starting role of Member or Org Admin, and send the invite. Invites appear in a Pending invites list with their expiry date until they're accepted, and you can revoke an invite at any time before that.
For each existing member, you can change their system role (Member or Org Admin) and, separately, assign one of your organization's custom roles for more granular permissions on top of or instead of the built-in role. Custom roles are defined on a separate Custom Roles screen, where an Org Admin picks exactly which permissions (grouped by area, such as projects, billing, or members) a role grants, then applies that role to members here. You can also remove a member from the organization entirely from this list.
Both the Members and Custom Roles pages require the Manage members permission; without it you'll see a no-access message rather than the member list. Note that Visibilitas guards against locking yourself out: the system prevents removing the organization's last remaining admin, and it will surface an error rather than silently failing if a role change would do that.
Project-level settings & access
Every project also has its own Settings area, separate from the organization-wide pages above. General settings cover the project's name, primary domain, target country and language (or multiple markets, if configured), industry, a list of target keywords, and any excluded domains the crawler should never visit. From the same page you can archive a project (pausing its scheduled crawls and jobs without deleting it) or restore an archived one, and organization members with the right permission can permanently delete a project.
Access controls which organization members can work on this specific project. An Org Admin (or anyone with Manage members) can add any existing member as a project collaborator, optionally marking them read-only so they can view the project without making changes, and can remove a collaborator's access at any time. This is separate from your organization-wide role: it lets you scope who touches a particular client site without changing anyone's overall permissions.
AI usage gives a project-scoped view into how much of your AI budget that project is consuming: total calls, tokens in/out, and cost, broken down by feature and shown as a recent activity log, filterable over the last 7, 30, or 90 days. It's a useful place to check if a project is approaching your plan's AI query limits before they affect other work.