Team: invite users and set what they can do

There are two routes to giving someone access to a project, and they write to the same place. Settings → 'Share this project' starts from the project and adds a person to it. The Team page (Project management → Team) starts from the people: it lists them all and assigns several projects to each one in a single move. A member added here gets real access, which also shows up in the settings of every project concerned.

Inviting someone

• The Invite button at the top right, then the person's email address.
• The role is picked from a list that spells out its reach: Editor — works on the project, Viewer — read only, Owner — everything, including sharing and deleting.
• Projects are assigned with pills: All projects, or a precise selection. 'All projects' keeps following the list as it grows.
• If the person has no account yet, one is created and an invitation goes out; access becomes active at their first sign-in.
• An email already in the team is refused — edit the existing row instead of recreating it.

The member table

• Columns: email, role, projects (and granted features), status, date added, actions.
• Edit opens the row: that is where you change the role and tick or untick projects.
• Unticking a project really removes access to it; the bin icon removes the member from all their projects at once, after a Confirm.
• Roles inherited from older versions (admin, member) are displayed automatically as Owner and Editor.

Enabled features and project cap

Below the projects, in edit mode, sits a set of switches specific to this page: it grants or withdraws capabilities for one person, regardless of what their plan provides.

• The eight switches: AI visibility (GEO scans), Google Search Console, Google Analytics 4, Bing Webmaster, CSV exports, AI generation (briefs, articles), Scan scheduling, BYOK plan (their own API keys).
• The Max projects field caps how many projects the person can create; left blank, their plan's limit applies.
• These settings take precedence over the plan: they exist to unblock one collaborator without moving them to another tier.

Viewer role: look without spending

• A viewer triggers no paid action: Refresh, Run analysis, Generate the AI analysis, Compute the value (Search Console), Analyze (local heatmap), Generate the missing analyses of a report, and the other buttons that start a new data pull.
• These buttons stay visible, but disabled, with the label « Reserved for editors ».
• The server refuses too: if a paid request still comes through (copied link, old page left open), it is refused with a clear message: « Your Viewer role does not allow starting a paid refresh. Ask an editor or the project owner. »
• Nothing to remove either: a viewer can remove neither an analysis from the history nor a keyword from the heatmap.
• They see everything else: data already collected, with its date, and analyses already generated.

Two safety rails

• The last owner of a project is never removed, even if you untick that project on their row: a project cannot end up with no owner.
• Role and project changes take effect immediately, without waiting for the person to sign in again.
• Removing a member does not delete their PivotSEO account, nor the projects they own elsewhere.