Power Pages - Portal Management App

Power Pages - Portal Management App

A powerful, model-driven app used to configure and customize the backend of your Power Pages site.

1. What Is the Portal Management App?

The Portal Management App is a dedicated model-driven app that gives administrators and developers full control over the configuration and backend structure of a Power Pages site. Unlike the visual Design Studio, this app exposes all advanced portal entities stored in Dataverse, enabling deeper customization and structured management of web pages, content, security, authentication, and custom logic.

2. When Should You Use It?

You use the Portal Management App when you need deeper configuration beyond what the Power Pages Design Studio offers. This includes managing advanced web roles, custom permissions, metadata, web templates, authentication providers, localized content, site settings, and Liquid templates. It is essential when building complex enterprise portals.

3. Key Features & Configuration Areas

The Portal Management App provides access to the entire backend structure of your site. Key configuration sections include:

  • Web Pages: Manage page hierarchy, content, templates, and visibility.
  • Web Templates: Control layout and structure using Liquid templates.
  • Content Snippets: Modify reusable blocks of text or HTML across the site.
  • Site Settings: Configure portal functionality, behaviors, and global parameters.
  • Web Files: Upload and manage documents, scripts, and media files.
  • Authentication: Configure identity providers such as Azure AD, LinkedIn, or Microsoft accounts.
  • Web Roles: Define roles to manage user access levels.
  • Table Permissions: Allow or restrict Dataverse table access (read, write, create, delete).
  • Content Access Levels: Protect specific pages, files, and forms.
  • Redirects: Manage URL rewrites and external/internal redirections.

4. Why the Portal Management App Is Important

While Power Pages Design Studio simplifies page building and visual design, the Portal Management App provides the "backend power". It offers granular control and complete portal customization. It is especially useful for:

  • Building enterprise-grade portals with advanced security requirements.
  • Customizing site layout with Liquid templates and dynamic content.
  • Configuring multilingual content and translations.
  • Managing complex user roles and data permissions.
  • Adding backend logic that Design Studio does not expose.

5. How to Access the Portal Management App

You can open the Portal Management App from:

  • Power Pages → Menu → Portal Management
  • Power Apps → Apps → Search for Portal Management
  • Direct link (environment-based): /apps?appid=<GUID> for your environment

Only users with proper Dataverse security roles (System Administrator, Maker, or custom elevated roles) can use the app effectively.

6. Who Uses the Portal Management App?

This app is primarily used by:

  • Developers customizing the portal using Liquid, HTML, CSS, or JS.
  • Admins managing permissions, roles, and authentication.
  • Site architects configuring structure and settings.
  • Power Pages advanced makers needing backend control.

Comments

Post a Comment

Popular posts from this blog

Part 1: Creating Code Apps in Power Apps - A step-by-step guide (with real errors I faced & how I fixed them)

Image
Intro In this post I’ll walk you through how I set up a code-based app for Power Apps (React/Vite front-end + Power Platform CLI for packaging/deployment), the exact errors I ran into, and how I solved them. If you want a hands-on, copy-paste able guide that covers Node versions, pac auth, environment issues, and packaging tips, this is for you. Prerequisites Microsoft 365 account with access to a Power Platform environment Node.js ( 20.19+  recommended LTS) VS Code Install power platform tools extension in VS Code. Steps: Step 1 : Open Visual Studio Code and launch the integrated terminal. Step 2: In the terminal, run the following commands one by one.   mkdir D:\CodeApps - Force cd D:\CodeApps npm create vite @latest myfirstapp -- -- template react - ts cd D:\CodeApps\myfirstapp npm install Initially, I ran the command: npm create vite@latest MyFirstApp -- --template react-ts This gave the error: Invalid package.json name The issue was caused because package...
Read more

Calling Microsoft Graph API from Power Automate Using Azure App Services – Step-by-Step Guide

Image
Step 1: You should have an Azure subscription, or if you have access to the Microsoft Entra Admin Center, you can create an app from there. This app can then be used in Power Automate to connect to Microsoft Graph API. Step 2: Click on "New registration" , provide a name for your app, assign the required API permissions (such as Microsoft Graph permissions), and then click "Register" to complete the app registration process. Step 3: After registration, you'll be redirected to the app's overview page. From there, navigate to the API permissions tab and click "Add a permission" to assign the necessary Microsoft Graph API permissions. Step 4: Select Microsoft Graph as the API, and based on your requirements, choose the appropriate permissions. In my case, I selected Application permissions , which do not require user sign-in and are suitable for background services or automation. Step 5: Select the required Microsoft Graph API permissions. Yo...
Read more

Step-by-Step Guide: Power Automate Custom Connector Using Graph API from Azure App Service

Image
Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...
Read more