Manage existing sites

Note

• Effective October 2022, Power Apps portals is Power Pages.
• This topic applies to legacy capabilities. For latest information, go to Microsoft Power Pages documentation.

If you created a site (portal) through Power Apps or Power Pages, it's visible when you sign in to Power Pages under Active sites on the Home page.

To manage a site, select More Commands (…) for the site and choose an action from the options in the dropdown.

Edit

Select Edit to open the site in Power Pages design studio. If your site was created with Power Apps portals (and you prefer), you can also select Edit in Power Apps portals to edit the content and components of the site.

Power Apps portals Studio requires a contact record with the email address portaluser@powerappsportals.com for some of its functionality to work. This contact record is automatically created when you edit the portal for the first time.

This contact record creation may fail in two scenarios:

• If you have one or more fields for the Contact table set as required.
• If your site has business logic (for example, synchronous plug-ins or workflows to restrict contact creation)

In either case, an error message displays:

Contact creation failed
A contact with an email address portaluser@powerappsportals.com must be created before you can edit your portal. Please create this contact manually.

When you see this error message, create a contact record manually with the email address portaluser@powerappsportals.com to resolve the error.

Preview

Opens the portal to preview the website. This option helps you to see the portal as it looks to your customers.

Alternately, you can also open the portal to browse the website by selecting Browse website in the Power Apps portals Studio to view the changes you have made to the website. The website opens in a new tab with URL of the website.

Share

Share your portal website address with users, with permissions to view it.

Share with internal users

To share the portal with internal users, you must first create a security role, and then assign users to the security role so they can use the portal.

Note

As a user in Microsoft Dataverse, if you do not have appropriate privileges on portal tables, you might see errors such as “You do not have access to view solutions in this environment.” or “You do not have access to view Website in this environment”. It is recommended that you are in a System Administrator security role in the corresponding Dataverse database.

Step 1: Create a security role

1. In the Share this portal pane, under Create a security role, select Security Roles. A list of all the configured security roles is displayed.

2. On the Actions toolbar, select New.

3. In the New Security Role window, enter the role name.

4. Set the privileges for all the tables used in your portal.

5. When you have finished configuring the security role, on the toolbar, select Save and Close.

For information on security roles and privileges, see Security roles and privileges.

Step 2: Assign users to the security role

1. In the Share this portal pane, under Assign users to the security role, select Users. A list of all users is displayed.

2. Select the user that you want to assign a security role to.

3. Select Manage Roles.

   Note

   If you are unable to see the Manage Roles button on the command bar, you must change the client by setting forceUCI to 0 in the URL. For example, https://<org_url>/main.aspx?pagetype=entitylist&etn=systemuser&forceUCI=0

4. In the Manage User Roles dialog box, select the security role that you created earlier, and then select OK.

Share with external users

Your portal should work anonymously and should be accessible by the external users. If you want to try advanced capabilities for managing roles and permissions for external users, see Configure a contact for use on a portal, Invite contacts to your portals, Create web roles for portals, Assign table permissions.

Admin center

Displays the portal settings and allows you to change the name of the portal. You can also go to set up licensing for your portal and advanced actions such as administering the portal though the Power Apps portals admin center and working with site settings.

Licensing

For production portals the Licensing for internal users and Licensing for external users section is visible in the portal's settings panel based on your environment licensing setup. Learn more about Power Apps per app plans, Pay-as-you-go.

Note

Licensing for internal users and Licensing for external users sections are not visible in portal settings panel when you open it from the portal's detail page tool bar Settings item.

Delete

Deletes the portal and hosted resources. When you delete a portal, its URL becomes inaccessible. Deleting a portal doesn't affect any portal configurations or solutions present in your environment, and they remain as-is. If you want to remove the portal configurations from your environment completely, delete the portal configurations manually. To delete, use the Portal Management app, and delete the corresponding website record for the portal.

Note

• If you don't have sufficient privileges to delete a portal, following error is displayed.
  Permission denied
You do not have sufficient privileges to delete the portal [Name] portal.
  You must have the System Administrator role to delete a portal. Also, you must be the owner of the portal application in Azure Active Directory. The user who creates the portal is by default the owner and can delete a portal. For information on adding yourself as an owner, see Add yourself as an owner of the Azure AD application.
• When you delete a portal, and create a new portal with a different URL, the authentication provider configuration must be configured for the new portal to work correctly. To configure the authentication provider, go to Get started with authentication configuration.

Completely delete a portal

To learn about how to delete a portal completely, go to Delete a portal.

Details

Displays details such as owner of the portal, date, and time when it was created and last modified, the URL of the portal, and identity provider settings.

Next steps

Power Apps portals Studio

See also

Understand how portals connects to Microsoft Dataverse environment
Understand and clear server-side cache in portals