You can give colleagues access to the Swifteq MCP Server by inviting them to your Swifteq account. For each person, you choose whether they connect to Zendesk with their own Zendesk login or use the connection your account already has, and what they are allowed to change.
In this Article
Own Login or Shared Connection
Inviting Users
Seats on the Team Plan
Checking a User's Connection, MCP Access and Write Access
Changing a User's Role, Connection or Write Access, or Removing a User
What Owners and Contributors Can Do
Things to Know
Own Login or Shared Connection
| Connection | What it means | When to use it |
|---|---|---|
| Own login (default, recommended) | The person connects their own Zendesk login the first time they open the MCP Server. Their own Zendesk role and group memberships apply, including Private Groups, and changes the AI assistant makes are shown in Zendesk as made by them. | Almost always, and whenever people in your team have different Zendesk permissions. |
| Shared connection | The person uses the Zendesk connection your account already has, with the permissions it was authorized with. Changes are shown in Zendesk as made by the person who authorized that connection. | Small teams who want everyone to act as the same Zendesk user. |
Inviting Users
- Sign in at https://agenthelper.swifteq.com/?product=mcpserver.
- Click the Profile button in the top right corner and select Invite Users.
- Enter the email address of the person you want to invite. You can enter up to 10 email addresses separated by commas.
- Select the Swifteq role: contributor (default) or owner.
- Select the Zendesk connection: Zendesk: own login (default) or Zendesk: shared connection.
When you select the shared connection, a short explanation displays below the form. - Select the write access: Write access: account default (default) or Write access: read only. Read only means the AI assistant cannot change anything in Zendesk for this person, whatever the account allows. You can change this later. Refer to Write Permissions for the MCP Server.
- Click Invite.
The user is added and receives an email with a link to activate their account and choose a password.
People on their own login then connect their Zendesk login. Refer to Connecting your Own Zendesk Login to the MCP Server.
Each person also needs to add the MCP Server to their own AI assistant. Refer to Connecting Claude to the MCP Server or Connecting ChatGPT to the MCP Server.
Seats on the Team Plan
On the free plan, everyone you invite can use the MCP Server, and they share your Zendesk account's free allowance. On the Team plan, each person needs a seat, and the top of the Users page shows how many seats are allocated and how many are available.
- When you invite people, Give each person a seat is selected by default and shows how many seats are free. Clear it to invite someone without a seat.
- If there are not enough seats, everyone is still invited: the first people get the free seats, and the rest join without one. We tell you who did not get a seat, and offer to add that many seats.
- To give someone a seat later, switch Seat on next to their name. If every seat is in use, that switch offers to add a seat for them.
- The account owner always holds a seat, and their switch cannot be turned off.
- Someone without a seat gets a clear message in their AI assistant asking them to contact the account owner. Nothing they do counts against your usage.
Adding and removing seats, and what happens to seats at renewal, is covered in MCP Server Pricing and Free Allowance.
Checking a User's Connection, MCP Access and Write Access
The list of users shows each person's role, Zendesk connection, MCP access and write access.
- Zendesk: own · not connected means the person has been invited on their own login but has not connected their Zendesk login yet. Their AI assistant cannot use the MCP Server until they do.
- Zendesk: own · connected means the person has connected their own Zendesk login.
- Zendesk: shared means the person uses the account's connection.
- The MCP access switch turns the person's access to the MCP Server on or off, without removing them from the account. On the Team plan the same switch is labelled Seat, and people without one show as No seat.
- The Write access column shows what the person is allowed to change. Account default means whatever the account allows. Read only, No public replies, No publishing, No user or organization changes, No macro changes, No merging and Restricted mean you have narrowed it for this person. Click the entry to change it.
Changing a User's Role, Connection or Write Access, or Removing a User
- On the Users page, click the vertical ellipsis next to the user and click Edit or Remove.
- When editing, select the role and the Zendesk connection for the MCP server.
- Under Write permissions for this person, keep Use the account settings, or select Restrict this person and switch off what they should not be able to do. A permission that is off for the whole account cannot be switched on here.
- Click OK.
Changes apply from the person's next request. A restriction you set for a person stays in place even if you later turn that permission on for the whole account. Refer to Write Permissions for the MCP Server.
If you select Remove, the user no longer has access to the account.
What Owners and Contributors Can Do
Both owners and contributors can use the MCP Server. Only owners can:
- Invite users, change a user's role or connection, and give or take back a seat (on the free plan, turn MCP access on or off).
- Change the write permissions for the whole account, and restrict what an individual person may change. Contributors can only turn permissions off for themselves. Refer to Write Permissions for the MCP Server.
- Disconnect the account from Zendesk.
Things to Know
- Users who were on the account before own logins were available stay on the shared connection until an owner changes them.
- You cannot invite someone who already has their own Swifteq account. The invite fails. Contact us with both email addresses and we will help move them onto your account.
- Settings are per Swifteq account. If colleagues signed up to separate Swifteq accounts, your settings do not apply to them, and each account is billed separately. Refer to How to Control Access and Subscription Cost for the MCP Server.
If you need help, please contact Swifteq support using the Live Chat or email support@swifteq.com.