![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\"){kind=icon}
<\/p><\/div>
- \n
- Removing your org from JumpCloud permanently removes Admins, Users, Groups, Devices, and any connections to resources like RADIUS and SSO apps. Org deletions are fully destructive and non-recoverable. <\/li>\n\n\n\n
- Deleting any object within your JumpCloud org is permanent. You can’t recover or restore an object once it’s been deleted. Please use caution when deleting or removing objects from JumpCloud.<\/li>\n<\/ul>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Prerequisites<\/strong>:<\/p>\n\n\n\n
- \n
- All of the users and orgs for your devices have to be deleted from JumpCloud before submitting your Org Delete Request. <\/li>\n\n\n\n
- A JumpCloud Admin associated with the org has to send in the request for deletion. JumpCloud might ask for additional information to confirm the identity of the person requesting the deletion.<\/li>\n<\/ul>\n\n\n\n
Considerations<\/strong>:<\/p>\n\n\n\n- \n
- Admins who are uncertain about the process or implications of removing JumpCloud from their orgs are advised to open a support case and address any concerns before requesting the deletion of their org. See Contact JumpCloud Support<\/a>. <\/li>\n\n\n\n
- Some deletions may require JumpCloud Finance approval, adding additional processing time. In these cases, the deletion won’t be processed until all financial items are resolved. Examples include contractual obligations, outstanding invoices, or other related issues. JumpCloud will work with you on resolution.<\/li>\n\n\n\n
- For security purposes, all org deletion requests are processed at JumpCloud’s Colorado (USA) location, during our normal business hours; Monday – Friday, 9 A.M. to 5 P.M. Mountain Daylight Time. <\/li>\n<\/ul>\n\n\n\n
Sending a Deletion Request<\/h2>\n\n\n\n
Before sending in your Org Delete request, follow these steps to ensure that the removal from JumpCloud goes smoothly. If you don’t follow these steps in proper order, your users or resources may have potential issues with access. <\/p>\n\n\n\n
Deleting Devices<\/h2>\n\n\n\n
JumpCloud requires all devices to be removed before an Org Deletion request is processed. If you’re using JumpCloud to manage devices, follow these steps:<\/p>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal: https:\/\/console.jumpcloud.com\/login<\/a>. <\/li>\n\n\n\n
- Go to DEVICE MANAGEMENT<\/strong> > Devices<\/strong>, then select the Devices <\/strong>tab.<\/li>\n\n\n\n
- Select all devices that you want to delete by clicking the checkbox next to the Status column.<\/li>\n\n\n\n
- Click delete<\/strong> in the top right corner of the page.<\/li>\n\n\n\n
- Confirm the number of devices you’re deleting, then click Delete<\/strong>. <\/li>\n<\/ol>\n\n\n\n
Deleting Devices in JumpCloud will uninstall the JumpCloud agent from all of your devices. The user, the user’s password, local files and profile data, and device policies will remain on the device after the JumpCloud Agent is uninstalled. <\/p>\n\n\n\n
Removing RADIUS Networks<\/h2>\n\n\n\n
If you have configured networking devices like WiFi or VPNs to authenticate using JumpCloud’s RADIUS-as-a-Service, you should first change the networking device’s configuration to point to either local authentication or another RADIUS Server not managed by JumpCloud. If you’re using JumpCloud’s RADIUS-as-a-Service, follow the steps below: <\/p>\n\n\n\n
- \n
- Reconfigure your networking device to either use local authentication protocols or <\/strong><\/em>reconfigure the device to point to another RADIUS server not managed by JumpCloud. <\/li>\n\n\n\n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to USER AUTHENTICATION <\/strong>> RADIUS<\/strong>. <\/li>\n\n\n\n
- Select your RADIUS server.<\/li>\n\n\n\n
- Click delete<\/strong>.<\/li>\n<\/ol>\n\n\n\n
By reconfiguring the Networking device to point to local authentication or another RADIUS Server, you are ensuring that users will have a method to authenticate to the network after your Jumpcloud Org Delete request has been processed. <\/p>\n\n\n\n
Reconfiguring LDAP Authentication<\/h2>\n\n\n\n
If you have configured applications or resources, like NAS, to authenticate using JumpCloud’s LDAP-as-a-Service, you should first change the resource’s configuration to point to either local authentication or another LDAP Server not managed by JumpCloud. If you’re using JumpCloud’s LDAP-as-a-Service, reconfigure your LDAP-enabled resource to either use local authentication or <\/strong><\/em>reconfigure the device to point to another LDAP server not managed by JumpCloud. <\/p>\n\n\n\n
By reconfiguring the LDAP-enabled resource to point to local authentication or another LDAP Server, you’re ensuring that users will have a method to authenticate to the resource after your Jumpcloud Org Delete request has been processed. <\/p>\n\n\n\n
Removing SSO Applications<\/h2>\n\n\n\n
If you have configured SSO apps, like Salesforce or Slack, to authenticate using JumpCloud, you should change the app’s configuration to either have the app handle authentication requests or repoint the SSO app to another SSO Identity Provider first. If you’re using JumpCloud as an Identity Provider for SSO apps, follow these steps: <\/p>\n\n\n\n
- \n
- Reconfigure your SSO app to either use its own authentication or <\/strong><\/em>reconfigure the SSO app to point to another SSO Identity Provider.<\/li>\n\n\n\n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to USER AUTHENTICATION<\/strong> > SSO<\/strong>.<\/li>\n\n\n\n
- Select the checkbox next to your SSO app connectors.<\/li>\n\n\n\n
- Click d<\/strong>elete<\/strong>. <\/li>\n\n\n\n
- Confirm the deletion by clicking yes, delete<\/strong>. <\/li>\n<\/ol>\n\n\n\n
By reconfiguring the SSO app device to point to itself for authentication or another SSO Identity Provider, you’re ensuring that users have a method to authenticate to the applications after your Jumpcloud Org Delete request has been processed.<\/p>\n\n\n\n
Deactivating Cloud Directory Integrations <\/h2>\n\n\n\n
If you have configured Cloud Directory Integrations like Google Workspace Sync, you should deactivate them before proceeding with the organization deletion request. To deactivate a Cloud Directory Integration:<\/p>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to DIRECTORY INTEGRATIONS<\/strong> > Cloud Directories<\/strong>.<\/li>\n\n\n\n
- In the list, select the Directory Integration you want to deactivate and click Deactivate Sync<\/strong>.<\/li>\n<\/ol>\n\n\n\n
Deleting Users<\/h2>\n\n\n\n
Deleting users is the last step before sending in your Org Deletion Request. You should’ve already configured each of the resources to handle authentication elsewhere, allowing users to maintain access to their resources after the Org Delete request has been processed.<\/p>\n\n\n\n
- Go to DIRECTORY INTEGRATIONS<\/strong> > Cloud Directories<\/strong>.<\/li>\n\n\n\n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to DEVICE MANAGEMENT<\/strong> > Devices<\/strong>, then select the Devices <\/strong>tab.<\/li>\n\n\n\n
- Admins who are uncertain about the process or implications of removing JumpCloud from their orgs are advised to open a support case and address any concerns before requesting the deletion of their org. See Contact JumpCloud Support<\/a>. <\/li>\n\n\n\n
![\"\"](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2023\/04\/AdminPortal_Settings_Delete_Org-1024x491.png\")
<\/figure>\n\n\n\n![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>