Connect with a team seat
How to connect Findip in Claude and ChatGPT once you hold a team seat. The registration steps are identical to a personal subscription. What differs is which account you sign in with — and that account is the seat your credits come from.
New to teams and seats? Read Team setup first; invitations, email verification, and seat assignment are covered there.
Three things that differ from a personal connection
Accept the invitation before you connect
A seat attaches to your account the moment you accept the invitation. Connecting beforehand connects you as a personal account; accepting later does not force you to recreate the connector, but the usage in between does not move onto the seat.
You connect by signing in, not with a key
An MCP connection does not use an API key. Register the connector, a browser popup opens, and you sign in to Findip and grant access — that is all. There is no shared team key and no per-team URL.
Usage lands on the seat you signed in with
Search credits are not one pool the team shares; they apply per seat. So the account you sign in with during setup is the one that owns that usage.
Shared MCP URL
Every member uses this same URL. The single line above is all the team admin has to hand out; everything else each member does with their own login.
Do not confuse this with the AI tool's own plan
Claude's Team and Enterprise plans, sold by Anthropic, and ChatGPT's Business, Enterprise, and Edu plans, sold by OpenAI, have nothing to do with a Findip team subscription. They do impose one constraint, though: in those workspaces an organization admin has to register or allow the connector first, so each section below covers that case separately.
Connecting in Claude
Confirm the invitation was accepted
In the browser you will connect from, sign in to Findip and check that a Team entry appears in the dashboard's left menu. If it does not, that account has no seat yet — go back to the invitation email and finish accepting first.
Add a custom connector
If your workspace is on Claude's Team or Enterprise plan, skip this step and follow the «When your organization has already registered the connector» section below instead.
In Claude's left sidebar, open Customize and go to Connectors. From the Add dropdown in the top right, choose Add custom connector.
Name it whatever you like and paste the URL above into the URL field. Leave the OAuth client ID and secret under Advanced settings empty.
Screenshots for each screen, plus tool permission settings, are in the Claude connection guide.
Sign in with the account that holds the seat
Clicking Add opens a Findip sign-in screen in a browser popup. Sign in there with the account that accepted the invitation. This is the one step where a team connection differs from a personal one.
If you juggle a work account and a personal one, check carefully which is signed in. If the popup does not appear, allow popups for claude.ai from the blocked-popup icon in the address bar and try again.
Turn it on in a conversation
Open Connectors from the + button in the composer and switch on the toggle with the name you chose in step 2. This is per conversation, so you can leave it off where you do not need it.
When your organization has already registered the connector
On Claude's Team and Enterprise plans, members cannot add custom connectors themselves. Once the organization owner registers Findip under Organization settings → Connectors, members only need to find Findip on the Not connected tab under Customize → Connectors and click Connect.
Signing in is still done by each member. The Managed authorization that Claude offers on Team and Enterprise plans covers only connectors wired to the organization's identity provider, and Findip does not support identity provider provisioning. Registering the connector at the organization level does not attach a Findip seat either, so sign in with the account that holds the seat, exactly as in step 3.
Connecting in ChatGPT
Confirm the invitation was accepted
Same as Claude. First check that the account shows a Team entry in the dashboard.
Connect Findip Patent
From Plugins in ChatGPT's left sidebar, search for findip, select Findip Patent, and click Connect in the top right. Findip is listed in the plugin directory, so there is no URL to type.
Screenshots for each screen are in the ChatGPT connection guide.
Sign in with the account that holds the seat
Click Sign in and, on the screen that follows, sign in with the Findip account that accepted the invitation and grant access. The button may not change right away, so refresh the page and confirm it becomes Start chat.
Turn it on in a new conversation
The conversation you installed the plugin from cannot use it. Start a new conversation, then type @ in the composer and pick Findip Patent — the most reliable way.
When a workspace admin has to allow it first
In ChatGPT Business, Enterprise, and Edu workspaces, members can only connect apps the admin has allowed. Your workspace admin needs to enable Findip Patent under Workspace settings → Apps & connectors.
In Enterprise and Edu workspaces the apps feature itself is off by default, so the admin has to turn that on first; in Business workspaces it is on by default, but allowing an individual app is still the admin's job.
Once it is allowed, follow the installation steps above as written — and here too, each member signs in with their own account.
Checking that the connection landed on your seat
After connecting, two checks make it unambiguous.
- Run one search from the AI tool, then look at the usage history on the dashboard Overview screen to confirm the search is recorded and credits were drawn. No record means you are signed in as a different account.
- Open Connected apps and confirm the app you just connected is listed. It shows the app name, scope, connection date, and last use, and Disconnect removes that app's access.
If you connected with the wrong account, disconnect from that tool's connector screen and sign in again with the account that holds the seat.
When your seat changes or you leave the team
If you leave the team, or the team admin removes you, the seat is released but the connector you registered in the AI tool stays. The account stays too, so disconnect it yourself from Connected apps or the tool's own connector screen if you want it cleared.
If the same account later receives a seat on another team, there is no need to recreate the connector. The connection is bound to the account, and credits follow whichever seat that account currently holds.
Common problems
Can the team admin connect on a member's behalf?
No. Registering the connector can be done for someone, but signing in to Findip only happens from each member's own account. Signing in with the team admin's account means that usage is drawn from the team admin's seat.
Do I need to issue an API key?
Not for an MCP connection. API keys are for integrating directly against the REST API, and each member issues their own on the dashboard API Keys screen. There is no shared team key.
Search works but credits are not coming off the team seat.
You are signed in as a different account with no seat. If that connection is missing from Connected apps, that confirms it. Disconnect in the tool and sign in again with the account that holds the seat.
Does every member have to connect separately?
Yes. Seats belong to people, so each member connects once for themselves. Even when the organization pre-registers the connector, signing in is individual.