> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/da/powershell-kommandoer/new-psuportalpage.md). # New-PSUPortalPage New-PSUPortalPage opretter en ny portalside i PowerShell Universal, sammensat af widgets og eventuelt begrænset af godkendelse og rolle. ## Synopsis Opretter en ny portalside i PowerShell Universal. ## Syntaks ``` New-PSUPortalPage -Name [-Description ] [-Widget ] [-Authenticated] [-Role ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies] [] ``` ## Beskrivelse Opretter en ny portalside i PowerShell Universal. Sider kan godkendes, begrænses til roller og sammensættes af widgets til portalkomponenter. ## Eksempler ### Eksempel 1 ```powershell PS C:\> New-PSUPortalPage -Name Operations -Description "Operations landing page" ``` Opretter en portalside med navnet Operations. ## Parametre ### -AppToken Angiver det app-token, der skal bruges ved godkendelse til PowerShell Universal Management API. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Authenticated Kræver godkendte brugere, før ressourcen kan tilgås eller kaldes. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ComputerName Angiver URL'en eller værtsnavnet for den ønskede PowerShell Universal-instans. Rene værtsnavne normaliseres til en `http://:5000`-URL. ```yaml Type: String Parameter Sets: (All) Aliases: Uri Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Legitimationsoplysninger til at logge på PowerShell Universal Management API. ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Description Angiver en beskrivelse af ressourcen. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Bruger den integrerede administrationsklient i processen, når cmdlet'en køres inde i PowerShell Universal. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Name Angiver navnet på ressourcen. ```yaml Type: String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Role Angiver en eller flere roller, der skal tildeles eller tillades. ```yaml Type: String[] Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Om cmdlet'en skal ignorere certifikatproblemer. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Bruger de aktuelle Windows-legitimationsoplysninger ved godkendelse til Management API. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Widget Angiver de portalkomponenter, der skal placeres på siden. ```yaml Type: PortalComponentInstance[] Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Cookies Genbruger og bevarer godkendelsescookies for den aktuelle PowerShell-session. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Denne cmdlet understøtter de fælles parametre: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable og -ProgressAction. Se [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216) for at få flere oplysninger. ## Input ### Ingen ## Output ### System.Object ## Noter ## Relaterede links ## Tilladelser Adgangstokenet kræver `portal.pages/create` for at oprette en portalside eksternt. Denne tilladelse tildeler ikke `portal.components/create`, som er påkrævet for at oprette definitioner af portalkomponenter. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/powershell-universal/da/powershell-kommandoer/new-psuportalpage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.