Skip to main content
Version: 1.28 (Current)

Update Portal

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens

Changes the name, administrator, keywords, description or email of a DNN portal (site). Leave the identifier empty to update the current portal. Empty parameters are left unchanged.

note

This action is part of the Portal Management add-on, which is installed and licensed separately (feature package PORTAL). If it isn't licensed, the action fails with a not-licensed error.

Typical Use Cases​

  • Rename a portal from an admin form
  • Hand a portal over to a new administrator
  • Update the portal's SEO keywords and description
  • Fill in details right after Create Portal

Don't use it to​

  • Change the portal alias or home directory. The action can't change them.
  • Clear a value. Empty parameters are skipped, so you can't set a field back to empty.
  • Change a page's settings. Use Update Page instead.
Action NameDescription
Load PortalReads the current values before you change them.
Create PortalCreates a portal.
Delete PortalDeletes a portal.
Load UserFinds the user ID to use as Administrator Id.

Input Parameter Reference​

ParameterDescriptionSupports TokensDefaultRequired
Portal IdentifierThe portal to update, as a portal ID (for example 3) or portal GUID. Leave it empty to update the current portal.Yesempty stringNo
Portal NameThe new portal name.Yesempty stringNo
Administrator IdThe user ID of the new portal administrator. A value that isn't a number is ignored.Yesempty stringNo
KeyWordsThe new keywords.Yesempty stringNo
DescriptionThe new description.Yesempty stringNo
EmailThe new portal email address.Yesempty stringNo

Output Parameters Reference​

This action doesn't produce any output tokens.

Considerations​

  • Only filled-in values change. Each parameter is applied only when it isn't empty after tokens are replaced. A token that resolves to empty leaves the old value in place.
  • Administrator Id isn't checked. The action doesn't check that the user exists or belongs to the portal.
  • The identifier must be an ID or a GUID. Anything else, or an ID that doesn't exist, makes the action fail with UpdatePortal action: Could not identify portal.
  • An empty identifier needs a current portal. If there's no portal in context, the action fails with Can not update current portal without portal into context.
  • There's no permission check in the action. Anyone who can run it can change any portal in the installation. Only put it where host users (superusers) or trusted administrators can reach it.

Examples​

tip

To understand how to use the below examples, please see Running Examples.

1. Rename a portal and change its administrator​

This action renames the portal in [SelectedPortalId] and makes the user in [NewAdminId] its administrator. Keywords, description and email stay as they are.

{
"Title": "Update Portal",
"ActionType": "UpdatePortal",
"Description": "Rename the portal and change its administrator",
"Condition": "[SelectedPortalId] != \"\"",
"Parameters": {
"PortalIdentifier": "[SelectedPortalId]",
"PortalName": "[NewPortalName]",
"AdministratorId": "[NewAdminId]"
}
}

Revised 09/27/2026