When developing web applications, one of the most common features you might need is the ability to dynamically redirect users to different subpages based on certain conditions, such as whether they are logged in or not. This ensures a smooth and personalized experience for users navigating your portal. In this guide, we’ll walk through how to set up redirection in Power Pages based on user authentication. Whether you’re building a public-facing portal or a member-only dashboard, this solution will help you ensure that users land on the right page based on their status. In our example, we want to redirect users based on their authentication status: By default, when users access your Power Pages portal, they land on the homepage. In this case, you want to check if the user is logged in and redirect them accordingly. We’ll use a Web Template in Power Pages. This template will contain the necessary JavaScript to check if the user is logged in and redirect them based on that. P.S. These below lines are included from the Default Studio Template. Don’t forget to include in your code. Next, create a Page Template and add the newly created Web Template. Go to Web Pages and update the Page Template as well. Click Save. And voila! The default landing page appears as soon as I access the website. With this simple solution, you can enhance the user experience by ensuring that visitors to your Power Pages portal are always directed to the content that’s most relevant to them. Happy Building! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com

The Sign In Page of a Power Apps Portal looks something like the image as shown below.  The components shown in different colors in the below image are on the portals login page, we cannot access the backend code of these components but we can rename disable enable these components so let’s see how to do this.  When you provision your power apps portal with the portal a “Portal Management” Model-driven app is also being deployed in your environments.  In this Portal Management app, there are site settings using which you can enable/disable the Sign in Page Components    Below is the list of site settings whose values (true/false) enable or disable components on the sign-in page.   Authentication/Registration/AzureADLoginEnabled – Enables / Disables Azure AD Button.  Authentication/Registration/ExternalLoginEnabled – Enables / Disables Externa SignIn Section  Authentication/Registration/Enabled – Enables / Disables the registration section.   Authentication/Registration/InvitationEnabled – Enables / Disables the invitaion redeem button   Authentication/Registration/LocalLoginEnabled – Enables / Disables the local login section   Authentication/Registration/OpenRegistrationEnabled – Enables / Disables Registration button.  Search/Enabled – Enables / Disabled search icon on the screen.  Hope this helps!  Thank you. 

Introduction: Shortcuts are used to place child nodes(child links) throughout the portal’s sitemap(navigation) which simply points to other nodes that exist in your sitemap, or to URLs external to your portal. Use Case: We have two parent pages- “Hardware” and “Support”.  Both are child pages of another page- “Home”.  “Support” page has a child page named- “Support Create”.  Let’s say we want to add the “Support Create” child page under “Hardware” in the Sitemap(navigation). Steps to create a shortcut Go to the “Portal Management” app. Go to Shortcuts Click on “+New” to create new record Enter following details on the form Attribute Details: Name: Name for the shortcut. For internal use only. Website: The website that the shortcut belongs to. Parent Page: The parent webpage of the shortcut entity in the sitemap. The shortcut will be added to the sitemap as a child of this page. External URL: URL outside of your organization. Web Page: internal webpage of the portal Web File: web file of the portal 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 entity will be shown instead. After adding all the details save the record Navigate to the portal to see changes you should see new child node named “Raise Support” under “Hardware” If you click on “Raise Support” it will redirect you to the “Create New Support” page NOTE: A shortcut can only have value in one of the ‘Target’ fields (External URL, Web Page, Web File). If more than one target attribute exists for a shortcut, the shortcut will just take the first one, ignoring all others.  Reference Article: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/place-child-nodes