This blog article will show you how to make a Power Automate Flow that replace the old OOTB (Out Of The Box) workflows and enable you to send portal invitation to contact with power automate flow – even to multiple contacts in one action. First…
To lock portal behind authentication can be handy for when you are developing the portal before launch and is a way to hide your portal from the world.
This post will show you how to enable the Blog feature on any portal type – and in so doing also showing you how to combine features cross portal types
Let me show you how to customize the sign-in and registration page in Power App Portals.
There is no obvious way to customize the sign-in and registration page in Power App Portals. The pages doesn’t exist in the Web Pages directory, and there is no Web Template. Even if you are logged into the portal as administrator the Portal Content Editor Toolbar doesn’t appear on these pages. There is no way – essentially – to edit the look and feel of these pages.
With the release of the new Power App Portal in this October ’19 Release we were introduced to a brand new Power Apps Portals Designer Interface. Microsoft marketed it as a new product under the slogan “Enable external access with portals” and it created some confusion. If you are still a little confused about the difference between Power Apps for external users and Power Apps Portals the link is to a blog post that will sort things out for you.
What is the difference between Power Apps for external users and Power Apps Portals? The short answer is; They are two different products.
The confusion comes from Microsoft Marketing choice of words when launching the October release updates “Enable external access with portals”
We use a theme framework that look lightly different from the OOTB (out of the box) experience. I need to add come classes and change the structure somewhat to make lists look like they should. I need a custom entity list. This is how: