If your team uses BulkPublish from Claude, auto-connect lets everyone in your organization use it straight away. Nobody has to sign in to BulkPublish from Claude or paste an API key: your organization vouches for each person, and BulkPublish connects them to your workspace.
Auto-connect works with Claude Team and Enterprise organizations. It can trust either your Claude organization or your company's identity provider.
Before you start
- You need to be the owner of the BulkPublish workspace. Admins and other roles can see the setting but cannot change it.
- On the Claude side, you need to be an Owner or Primary Owner of your Claude organization.
- Everyone who should be connected needs to be a member of your BulkPublish workspace, with a verified email address that matches the one they use in Claude. Invite anyone who is missing from Team first.
Setting it up with your Claude organization
- In Claude, open Organization settings, then Connectors, find BulkPublish and choose Set up auto-connect. For Identity source, choose Claude-issued. Claude shows an Issuer URL. Copy it.
- In BulkPublish, open API in the sidebar and find MCP Auto-connect, below API Keys.
- Paste the Issuer URL into Trusted issuer URL and choose Save.
- Switch on Connect members automatically.
- Back in Claude, choose Run test under Connection status to check that it works.
From then on, when a member of your Claude organization uses BulkPublish in Claude, they are connected to your BulkPublish workspace as themselves, with their own role.
Setting it up with your identity provider
If your organization signs in to Claude through its identity provider, choose IdP-managed in Claude's auto-connect setup instead, and follow the steps it shows to register BulkPublish with your identity provider. Then paste your identity provider's issuer URL into Trusted issuer URL in BulkPublish and switch on Connect members automatically.
Several workspaces, one organization
If more than one of your BulkPublish workspaces trusts the same issuer, BulkPublish needs to know which workspace a person belongs in. Copy the Workspace ID shown under MCP Auto-connect and enter it as the Tenant ID in Claude's auto-connect setup for that workspace. Without it, sign-ins for that issuer are refused rather than sent to the wrong workspace.
Who gets connected
- Only people who are already members of the workspace. Auto-connect never creates an account or adds anyone to your team.
- A person is matched by their verified email address. If their address in BulkPublish is not verified, or differs from the one their organization signs them in with, they are not connected. They can still connect the usual way.
- Each person acts with their own role. A Viewer stays a Viewer.
- An auto-connected assistant can work with posts, media, analytics and your inbox. It cannot manage your team, billing, workspace settings or API keys.
Turning it off
Switch off Connect members automatically. Everyone who was connected this way is disconnected straight away, not when their session would have ended. Changing the Trusted issuer URL does the same for everyone who was connected through the old one.
Removing someone from your BulkPublish workspace also ends their access at once. Removing them from your Claude organization stops new connections, and any session they already had ends within the hour.
Each person's connection is also listed under Connected apps as BulkPublish MCP (auto-connect). While auto-connect is on for the workspace, disconnecting it there ends the current session, and the next time that person uses BulkPublish in Claude they are connected again.
When it does not connect
- Run test fails in Claude: check that the Issuer URL in BulkPublish is exactly the one Claude shows, including any slash at the end, and that Connect members automatically is on.
- One person is not connected: check that they are a member of the workspace and that their email address in BulkPublish is verified and the same as their Claude account's.
- Nobody in a second workspace is connected: enter that workspace's ID as the Tenant ID, as described above.
Still stuck? Contact support from the chat button in the app and tell us your workspace ID.