Bottom line: DSE recommends treating application detachment, organization removal and recording disposition as separate acceptance decisions. Before changing a camera’s portal state, identify which service owns it and what must happen to its associated recordings.
\nThe Cloud Portal device-management article says a device currently claimed by an application must first be unclaimed by that application before it can be removed from the organization.
\nIn the same removal section, Hanwha states that a device with associated recordings changes from Online to Deactivated. The article says that device can be reclaimed while maintaining the camera’s previous settings and recordings. This is a documented portal-state and recording-association distinction, not a statement that selecting Remove erases recorded material.
\nThe article does not establish a legal retention period, irreversible erasure or transfer of material between unrelated organizations. It also does not guarantee that every reclaim choice preserves the same information. Resolve recording ownership and the intended reclaim path separately rather than treating a portal label as a complete data-handling policy.
\nThe following steps are DSE recommendations based on the captured Cloud Portal workflow.
\nWrite a short transition plan identifying the camera, organization, linked application and intended after-state. Separate the request to stop using a device from any request to remove its data. Name the person responsible for each decision so a service technician does not have to infer the owner’s intention from a removal ticket.
\nBefore changing the claim, record the relevant device identity and associated application. Have the recording owner identify any material that must remain accessible and the approved way to verify it. Preserve only the necessary administrative evidence; do not place footage or account secrets in a general change record.
\nFollow the current documented sequence for the authorized operation. At each stage, compare the observed application and organization state with the plan. If a reclaim is intended, record the precise choice made and require the owner to confirm the expected settings and recordings afterward. Stop if the requested state cannot be reconciled with the retention decision.
\nUse a controlled test or an approved device change to collect before-and-after evidence from the application and Cloud Portal. Record whether the application claim was removed, the state displayed for the device and the outcome of any authorized reclaim.
\nVerify the recording requirement through the approved viewing workflow rather than relying only on the device row. Keep configuration recovery, recording access and any separately authorized deletion checks as distinct results. Escalate missing material or an unexpected state before repeating the operation.
\nRetain the device identity, change authority, intended transition, observed states and recording-owner confirmation together. Do not close a data-deletion request merely because the equipment no longer appears active in its former application.
\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: DSE recommends treating application detachment, organization removal and recording disposition as separate acceptance decisions. Before changing a camera’s portal state, identify which service owns it and what must happen to its associated recordings.\nSource fact: removal can leave a reclaimable device\nThe Cloud Portal device-management article says a device currently claimed by an application must first be unclaimed by that application before it can be removed from the organization.\nIn the same removal section, Hanwha states that a device with associated recordings changes from Online to Deactivated. The article says that device can be reclaimed while maintaining the camera’s previous settings and recordings. This is a documented portal-state and recording-association distinction, not a statement that selecting Remove erases recorded material.\nWhat the source does not establish\nThe article does not establish a legal retention period, irreversible erasure or transfer of material between unrelated organizations. It also does not guarantee that every reclaim choice preserves the same information. Resolve recording ownership and the intended reclaim path separately rather than treating a portal label as a complete data-handling policy.\nApplicability questions\n\nWhich organization and application currently claim the camera?\nWhat recordings are associated with the device, and who owns the retention decision?\nIs the goal to stop application use, recover an existing device or retire equipment?\nWhich settings and recordings must remain available afterward?\nWho is authorized to make the change and verify the resulting state in each relevant service?\n\nDSE recommendation: record the intended transition\nThe following steps are DSE recommendations based on the captured Cloud Portal workflow.\nWrite a short transition plan identifying the camera, organization, linked application and intended after-state. Separate the request to stop using a device from any request to remove its data. Name the person responsible for each decision so a service technician does not have to infer the owner’s intention from a removal ticket.\nBefore changing the claim, record the relevant device identity and associated application. Have the recording owner identify any material that must remain accessible and the approved way to verify it. Preserve only the necessary administrative evidence; do not place footage or account secrets in a general change record.\nFollow the current documented sequence for the authorized operation. At each stage, compare the observed application and organization state with the plan. If a reclaim is intended, record the precise choice made and require the owner to confirm the expected settings and recordings afterward. Stop if the requested state cannot be reconciled with the retention decision.\nVerification and evidence\nUse a controlled test or an approved device change to collect before-and-after evidence from the application and Cloud Portal. Record whether the application claim was removed, the state displayed for the device and the outcome of any authorized reclaim.\nVerify the recording requirement through the approved viewing workflow rather than relying only on the device row. Keep configuration recovery, recording access and any separately authorized deletion checks as distinct results. Escalate missing material or an unexpected state before repeating the operation.\nRetain the device identity, change authority, intended transition, observed states and recording-owner confirmation together. Do not close a data-deletion request merely because the equipment no longer appears active in its former application.\nOfficial references\n\nCloud Portal: How do I manage devices? — Hanwha Vision; application detachment, removal and reclaim sections.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: DSE recommends treating application detachment, organization removal and recording disposition as separate acceptance decisions. Before changing a camera’s portal state, identify which service owns it and what must happen to its associated recordings.\n\n## Source fact: removal can leave a reclaimable device\n\nThe [Cloud Portal device-management article](https://supportportal.hanwhavision.com/global/knowledge-base/47256959314835) says a device currently claimed by an application must first be unclaimed by that application before it can be removed from the organization.\n\nIn the same removal section, Hanwha states that a device with associated recordings changes from Online to Deactivated. The article says that device can be reclaimed while maintaining the camera’s previous settings and recordings. This is a documented portal-state and recording-association distinction, not a statement that selecting Remove erases recorded material.\n\n## What the source does not establish\n\nThe article does not establish a legal retention period, irreversible erasure or transfer of material between unrelated organizations. It also does not guarantee that every reclaim choice preserves the same information. Resolve recording ownership and the intended reclaim path separately rather than treating a portal label as a complete data-handling policy.\n\n## Applicability questions\n\n- Which organization and application currently claim the camera?\n\n- What recordings are associated with the device, and who owns the retention decision?\n\n- Is the goal to stop application use, recover an existing device or retire equipment?\n\n- Which settings and recordings must remain available afterward?\n\n- Who is authorized to make the change and verify the resulting state in each relevant service?\n\n## DSE recommendation: record the intended transition\n\nThe following steps are DSE recommendations based on the captured Cloud Portal workflow.\n\nWrite a short transition plan identifying the camera, organization, linked application and intended after-state. Separate the request to stop using a device from any request to remove its data. Name the person responsible for each decision so a service technician does not have to infer the owner’s intention from a removal ticket.\n\nBefore changing the claim, record the relevant device identity and associated application. Have the recording owner identify any material that must remain accessible and the approved way to verify it. Preserve only the necessary administrative evidence; do not place footage or account secrets in a general change record.\n\nFollow the current documented sequence for the authorized operation. At each stage, compare the observed application and organization state with the plan. If a reclaim is intended, record the precise choice made and require the owner to confirm the expected settings and recordings afterward. Stop if the requested state cannot be reconciled with the retention decision.\n\n## Verification and evidence\n\nUse a controlled test or an approved device change to collect before-and-after evidence from the application and Cloud Portal. Record whether the application claim was removed, the state displayed for the device and the outcome of any authorized reclaim.\n\nVerify the recording requirement through the approved viewing workflow rather than relying only on the device row. Keep configuration recovery, recording access and any separately authorized deletion checks as distinct results. Escalate missing material or an unexpected state before repeating the operation.\n\nRetain the device identity, change authority, intended transition, observed states and recording-owner confirmation together. Do not close a data-deletion request merely because the equipment no longer appears active in its former application.\n\n## Official references\n\n- [Cloud Portal: How do I manage devices?](https://supportportal.hanwhavision.com/global/knowledge-base/47256959314835) — Hanwha Vision; application detachment, removal and reclaim sections.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/", "url": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-28" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Distinguish Hanwha Cloud Portal deactivation from data deletion", "item": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/#article", "identifier": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/", "url": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/", "headline": "Distinguish Hanwha Cloud Portal deactivation from data deletion", "description": "Review application claims and associated recordings before choosing organization removal or reclaim in Cloud Portal.", "abstract": "Review application claims and associated recordings before choosing organization removal or reclaim in Cloud Portal.", "articleBody": "Bottom line: DSE recommends treating application detachment, organization removal and recording disposition as separate acceptance decisions. Before changing a camera’s portal state, identify which service owns it and what must happen to its associated recordings.\nSource fact: removal can leave a reclaimable device\nThe Cloud Portal device-management article says a device currently claimed by an application must first be unclaimed by that application before it can be removed from the organization.\nIn the same removal section, Hanwha states that a device with associated recordings changes from Online to Deactivated. The article says that device can be reclaimed while maintaining the camera’s previous settings and recordings. This is a documented portal-state and recording-association distinction, not a statement that selecting Remove erases recorded material.\nWhat the source does not establish\nThe article does not establish a legal retention period, irreversible erasure or transfer of material between unrelated organizations. It also does not guarantee that every reclaim choice preserves the same information. Resolve recording ownership and the intended reclaim path separately rather than treating a portal label as a complete data-handling policy.\nApplicability questions\n\nWhich organization and application currently claim the camera?\nWhat recordings are associated with the device, and who owns the retention decision?\nIs the goal to stop application use, recover an existing device or retire equipment?\nWhich settings and recordings must remain available afterward?\nWho is authorized to make the change and verify the resulting state in each relevant service?\n\nDSE recommendation: record the intended transition\nThe following steps are DSE recommendations based on the captured Cloud Portal workflow.\nWrite a short transition plan identifying the camera, organization, linked application and intended after-state. Separate the request to stop using a device from any request to remove its data. Name the person responsible for each decision so a service technician does not have to infer the owner’s intention from a removal ticket.\nBefore changing the claim, record the relevant device identity and associated application. Have the recording owner identify any material that must remain accessible and the approved way to verify it. Preserve only the necessary administrative evidence; do not place footage or account secrets in a general change record.\nFollow the current documented sequence for the authorized operation. At each stage, compare the observed application and organization state with the plan. If a reclaim is intended, record the precise choice made and require the owner to confirm the expected settings and recordings afterward. Stop if the requested state cannot be reconciled with the retention decision.\nVerification and evidence\nUse a controlled test or an approved device change to collect before-and-after evidence from the application and Cloud Portal. Record whether the application claim was removed, the state displayed for the device and the outcome of any authorized reclaim.\nVerify the recording requirement through the approved viewing workflow rather than relying only on the device row. Keep configuration recovery, recording access and any separately authorized deletion checks as distinct results. Escalate missing material or an unexpected state before repeating the operation.\nRetain the device identity, change authority, intended transition, observed states and recording-owner confirmation together. Do not close a data-deletion request merely because the equipment no longer appears active in its former application.\nOfficial references\n\nCloud Portal: How do I manage devices? — Hanwha Vision; application detachment, removal and reclaim sections.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-28T23:23:15+00:00", "dateModified": "2026-10-28T23:23:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/distinguish-hanwha-cloud-portal-deactivation-from-data-deletion/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Distinguish Hanwha Cloud Portal deactivation from data deletion" }, "articleSection": [ "Business Continuity", "Video Surveillance" ], "keywords": [ "Business Continuity", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 563, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Hanwha Vision: Cloud Portal: How do I manage devices?", "url": "https://supportportal.hanwhavision.com/global/knowledge-base/47256959314835" } } ] } }