{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
        "slug": "scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state",
        "url": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/"
        },
        "title": "Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state",
        "summary": "Use Set up Windows LAPS in the LAPS properties dialog to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T16:59:10+00:00",
        "modified_at": "2026-08-27T17:41:22+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 600,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Set up Windows LAPS in the LAPS properties dialog",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "Set up Windows LAPS in the LAPS properties dialog",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Use this document to resolve one bounded operational decision: Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface\" target=\"_blank\" rel=\"noopener noreferrer\">Set up Windows LAPS in the LAPS properties dialog</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “Learn how to use the LAPS properties dialog in the Windows Server Active Directory Users and Computers management snap-in to configure Windows Local Administrator Password Solution (Windows LAPS) for Windows Server Active Directory.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Windows LAPS snap-in availability, Microsoft states: “The Windows LAPS-enabled Active Directory Users and Computers management snap-in is available on Windows Server platforms that have been patched with the Windows LAPS feature.” The research record locates this support at <strong>Windows LAPS snap-in availability</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Windows LAPS snap-in availability</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, including exceptions?</li>\n<li>What baseline for Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation.</p>\n<p>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>Introduction below H1</strong>; <strong>Windows LAPS snap-in availability</strong> adjacent to the sanitized artifacts used for comparison. Prefer policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, with enough identity and timing data for an independent recheck.</p>\n<p>Label this evidence set <strong>DSE-20260827-496</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface\" target=\"_blank\" rel=\"noopener noreferrer\">Set up Windows LAPS in the LAPS properties dialog</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Set up Windows LAPS in the LAPS properties dialog from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “Learn how to use the LAPS properties dialog in the Windows Server Active Directory Users and Computers management snap-in to configure Windows Local Administrator Password Solution (Windows LAPS) for Windows Server Active Directory.” The research record locates this support at Introduction below H1.\nAt Windows LAPS snap-in availability, Microsoft states: “The Windows LAPS-enabled Active Directory Users and Computers management snap-in is available on Windows Server platforms that have been patched with the Windows LAPS feature.” The research record locates this support at Windows LAPS snap-in availability.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Windows LAPS snap-in availability, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, including exceptions?\nWhat baseline for Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nKeep the source locations Introduction below H1; Windows LAPS snap-in availability adjacent to the sanitized artifacts used for comparison. Prefer policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-496 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nSet up Windows LAPS in the LAPS properties dialog — Microsoft",
        "content_markdown": "Use this document to resolve one bounded operational decision: Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Set up Windows LAPS in the LAPS properties dialog](https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “Learn how to use the LAPS properties dialog in the Windows Server Active Directory Users and Computers management snap-in to configure Windows Local Administrator Password Solution (Windows LAPS) for Windows Server Active Directory.” The research record locates this support at Introduction below H1.\n\n- At Windows LAPS snap-in availability, Microsoft states: “The Windows LAPS-enabled Active Directory Users and Computers management snap-in is available on Windows Server platforms that have been patched with the Windows LAPS feature.” The research record locates this support at Windows LAPS snap-in availability.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Windows LAPS snap-in availability, which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, including exceptions?\n\n- What baseline for Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation.\n\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nKeep the source locations Introduction below H1; Windows LAPS snap-in availability adjacent to the sanitized artifacts used for comparison. Prefer policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, with enough identity and timing data for an independent recheck.\n\nLabel this evidence set DSE-20260827-496 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [Set up Windows LAPS in the LAPS properties dialog](https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface) — Microsoft"
    },
    "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/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state",
                        "item": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/#article",
                "identifier": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/",
                "headline": "Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state",
                "description": "Use Set up Windows LAPS in the LAPS properties dialog to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Set up Windows LAPS in the LAPS properties dialog to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Set up Windows LAPS in the LAPS properties dialog from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “Learn how to use the LAPS properties dialog in the Windows Server Active Directory Users and Computers management snap-in to configure Windows Local Administrator Password Solution (Windows LAPS) for Windows Server Active Directory.” The research record locates this support at Introduction below H1.\nAt Windows LAPS snap-in availability, Microsoft states: “The Windows LAPS-enabled Active Directory Users and Computers management snap-in is available on Windows Server platforms that have been patched with the Windows LAPS feature.” The research record locates this support at Windows LAPS snap-in availability.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Windows LAPS snap-in availability, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, including exceptions?\nWhat baseline for Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nKeep the source locations Introduction below H1; Windows LAPS snap-in availability adjacent to the sanitized artifacts used for comparison. Prefer policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-496 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nSet up Windows LAPS in the LAPS properties dialog — Microsoft",
                "datePublished": "2026-08-27T16:59:10+00:00",
                "dateModified": "2026-08-27T17:41:22+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/"
                },
                "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/scope-set-up-windows-laps-in-the-laps-properties-dialog-in-observed-ad-dns-state/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Scope Set up Windows LAPS in the LAPS properties dialog in observed AD/DNS state"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 600,
                "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": "Set up Windows LAPS in the LAPS properties dialog",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-user-interface"
                }
            }
        ]
    }
}