Place child nodes by using shortcuts for portals


Effective October 12, 2022, Power Apps portals is Power Pages. More information: Microsoft Power Pages is now generally available (blog)
We will soon migrate and merge the Power Apps portals documentation with Power Pages documentation.

Use shortcuts to place child nodes throughout your portal's sitemap that simply point to other nodes that exist in your sitemap, or to URLs external to your portal. In other words, webpages, web files, events, and forums can all be considered "solid" nodes of your portal's sitemap: they are added to your sitemap and when you navigate to them, you see the actual content of those nodes directly. Shortcuts, on the other hand, can be considered “intangible” nodes: they are also added to the sitemap (unlike web links, which are not), but when you navigate to them, you see the content for the target "solid" node that the shortcut points to, and that content is rendered by the page template for that node.

Manage shortcuts

Creating, editing, and deleting shortcuts can be done within Power Apps portals.

  1. Open the Portal Management app.

  2. Go to Portals > Shortcuts.

  3. To create a shortcut, select New.

  4. To edit an existing shortcut, select the existing shortcut in the grid.

  5. Enter values for the fields provided.

  6. Select Save & Close

Attributes and relationships

Name Description
Name A Descriptive Name for the shortcut. For internal use only.
Website The website that the shortcut belongs to.
Parent Page The parent webpage of the shortcut table in the sitemap. The shortcut will be added to the sitemap as a child of this page.
External URL Target of the shortcut to a URL of a resource outside of your organization.
Web Page Target of the shortcut to an internal webpage.
Web File Target of the shortcut to a web file.
Event Target of the shortcut to an event.
Forum Target of the shortcut to a forum.
Title The title for the shortcut. This is the name that will appear in the sitemap and child navigation view areas. If left blank, the title (or name) of the target table will be shown instead.
Description A description to appear in child nav views. Optional.
Display Order The front-side editable order that the shortcut will appear in sitemap and child nav views, in relation to other nodes in the site map.
Disable Shortcut Target Validation If unchecked, the security of the shortcut will be based on the target. Otherwise, it will be based on the parent. For more details, see Security below.


A shortcut needs only to have one of the 'Target' fields (External URL, Web Page, Survey, Web File, Event, Forum) assigned a value, and a shortcut will only have one target. For example, a shortcut does not point at both a Web Page and a survey, or an External URL and a Web File. If more than one target attribute exists for a shortcut, the shortcut will just take the first one, ignoring all others. The order of priority for which target will be chosen is reflected on the main shortcut form. So, it will first check if there exists an External URL for the shortcut, and if there is, then the shortcut's target will be the External URL and all other target attributes will be ignored. If there is no External URL, then the shortcut will check the Web Page, then the Survey, Web file, Event, and finally Forum.

Secure shortcuts

Security for shortcuts can be based either on the parent page of the shortcut or on the target of the shortcut. This will determine whether the shortcut will be visible in the sitemap. Naturally, if security is based off the parent, the write access of the target of the shortcut will still determine whether front-side editing will function after the shortcut has been used to navigate to the target of the shortcut. Therefore, shortcut security only affects navigation and edit rights for front-side editing of shortcuts. The security method used is specific to the shortcut. If you leave the Boolean value Disable Shortcut Target Validation unselected, the security of the shortcut will be based on the target; otherwise, it will be based on the parent.

After the shortcut table has been created, it will appear in your website. In the above example, Basic Site has two additional pages, Page One and Page Two. Page Two Is a Child of Page One, which is a Child of the Home Page. Additionally, there is a shortcut that is a child of the Home page which points to Page Two.