Deleting a connection
What deleting a mailbox, generic or vendor connection removes, and what it leaves alone.
Who can do thisWorkspace Administrator
Deleting a connection removes it from the workspace for good. There is no recycle bin and no undo. If you only want the runs to stop for a while, pause the connection instead: see A connection's page: figures, Pause and Resume.
The Integration Hub is in English only, so its labels are quoted in English in the Danish articles too.
Delete a connection
- Open Connections in the left rail.
- Find the connection. Use Search connections or the view pills if the list is long.
- Click Delete at the end of the row.
- Read the dialog. It says what this kind of connection loses (see below).
- Click Delete to confirm. The row disappears from the list.
A shared mailbox, Intune, Jamf Pro or REST connection can only be deleted from the list. Its own page has no Delete. The Webmercs vendor connection is the exception: it has Delete both on its row and on its page, and deleting from the page shows the toast "Vendor connection deleted" and takes you back to the list.
What each kind of deletion removes
| Connection | Dialog | What happens |
|---|---|---|
| Shared mailbox | Delete mailbox connection | "This stops collecting mail from the mailbox and removes its stored credential. Tickets already created are not affected." Mail that arrives afterwards stays in the mailbox and does not become a ticket. |
| Microsoft Intune, Jamf Pro, Generic REST / JSON | Delete connector integration | "This removes the connector integration." The connection goes with its schedule, mapping and webhook, and so does a client secret the Hub stored for it. |
| Webmercs vendor connection | Delete vendor connection | "Flexshop stops sending approved requests to this shop, and the stored password is removed. Orders already placed at the vendor are not affected." |
After a Webmercs connection is deleted, the workspace has no enabled vendor connection. Approved Flexshop requests are then not sent anywhere: Flexshop marks them as not sent, and an administrator can order them by hand. The Flexshop articles describe that side.
Before you delete
- Moving a mailbox? Set up and enable the new mailbox connection first, check that tickets arrive, and then delete the old one. That way no mail falls in the gap.
- Replacing a secret? You do not need to delete anything. Rotate the credential instead: see Credentials: expiry dates and rotation.
- Unsure whether it is still used? Check Last run on the connection's page and the Usage page. A connection you pause can always be resumed later; a deleted one must be set up from scratch.
- Clean up outside the Hub. Deleting the connection does not touch the outside system. Remove the app registration, service account, mail user or Webmercs API user there if nothing else needs it.
Each workspace can have at most 50 connections, so deleting one you no longer use also frees a place.
What cannot be deleted here
- Rows in the group "Platform - run by Juvaro (N)" have no Delete. They belong to user provisioning and are managed in the Workspace portal. See Single sign-on and directory sync cards.
- Members see no Delete at all. See What members see in the Hub.
If the deletion is refused
| Message | What it means |
|---|---|
| "403 - Only a workspace administrator can change connections. Ask an administrator of this workspace." | You are not a Workspace Administrator, or your role was removed a moment ago. |
| "Only a workspace administrator can view or change the vendor connection." | The same, for the Webmercs connection. |
| "This vendor connection no longer exists. It may have been deleted." | Someone else deleted it first. Reload the list. |
| "This connection's stored settings cannot be read, so nothing was deleted. An operator must repair the stored connection before it can be deleted." | The Hub could not find the stored secret to remove, so it deleted nothing. Contact Juvaro support. |