Update general navigation profle docs as well

Author: WimJongeneel

content/en/docs/refguide/modeling/app-explorer/app/navigation/_index.md

@@ -25,8 +25,9 @@ The core of Mendix's navigation model is founded on the following profiles:
 * Phone web
     * Phone web offline
 * Native mobile (tablet & phone)
+* Embedded (Beta)
 
-Users that access the app via a particular device type are automatically redirected to the homepage of the appropriate profile based on the profile type (for details, see the [Redirection to Profiles](#redirection) section below).
+Users that access the app via a particular device type are automatically redirected to the homepage of the appropriate browser or mobile profile based on the profile type (for details, see the [Redirection to Profiles](#redirection) section below). The Embedded profile is not selected through device detection. It is used when a host application loads the embedded client.
 
 The device type of the currently logged-in user is available in [microflows](/refguide/microflows/) as the `$currentDeviceType` variable. The type of this variable is the [enumeration](/refguide/enumerations/) `System.DeviceType`, which has the values `Phone`, `Tablet`, and `Desktop`. You can use `$currentDeviceType` to perform different actions based on the device type. A typical example is to show different pages based on the device type.
 
@@ -56,6 +57,12 @@ The Mendix app will run in [offline-first](/refguide/offline-first/) mode. This
 You are required to enable anonymous users in your app's security settings and include anonymous user roles on native login pages. This is because there is no built-in login screen in the native profile; login pages are modeled as regular native pages. 
 {{% /alert %}}
 
+### Embedded
+
+The Embedded profile lets you use a Mendix web app as a component inside another web application. The host application loads the embedded client and owns browser-level navigation, while the Mendix app renders and navigates inside its mounted region.
+
+The Embedded profile defines a default home page and can also define an error page. When the configured home page expects page parameters, the host application can pass them through the `parameters` object in `render(...)`. For more information, see [Embedding the Client](/refguide/mendix-client/embedding-the-client/).
+
 ## Redirection to Profiles {#redirection}
 
 Mendix Runtime automatically redirects users to the home page of the appropriate device type based on the device they are using. This happens by examining the `User-Agent` string that is sent by the device. The default configuration for this redirection is as follows:
@@ -98,6 +105,8 @@ The default home page indicates which [page](/refguide/page/) or [microflow](/re
 The default home page is visible to all unauthenticated users.
 {{% /alert %}}
 
+For the Embedded profile, the default home page is the first page shown when the host application calls `render(...)`.
+
 #### Role-Based Home Pages{#role-based}
 
 By using role-based home pages, you can show different home pages for different users. If a user logs in, the first role-based home page of which the user role matches the user role of the user is displayed. If no match is found, the default home page is used.
@@ -108,6 +117,10 @@ For each role-based home page, you can specify the user role it applies to and t
 
 The fallback page is a page or microflow that can be used to customize the application's behavior when trying to access a [microflow](/refguide/microflow/#url) or [page](/refguide/page-properties/#url) URL that does not exist. For more information, see [Setting a Fallback Page](/refguide/setting-up-the-navigation-structure/#fallback) in *Setting Up Navigation*.
 
+#### Error Page
+
+For Embedded profiles, you can configure an error page. This page is shown when the embedded app cannot open the configured home page during startup or navigation. Examples include page parameter values passed through `render(...)` that do not match the expected parameter types, or a configured home page that is not accessible for the signed-in user. For more information, see [Embedding the Client](/refguide/mendix-client/embedding-the-client/).
+
 ### Authentication {#authentication}
 
 If a user, [anonymous](/refguide/anonymous-users/) or authenticated, tries to access a resource to which the user has no access, the configured [sign-in page](/refguide/authentication-widgets/) will be displayed, prompting the user to sign in.
@@ -145,4 +158,5 @@ For more details on the settings and when to use them, see the [Offline-First Re
 ## Read More
 
 * [App Explorer](/refguide/app-explorer/)
+* [Embedding the Client](/refguide/mendix-client/embedding-the-client/)
 * [Navigation Tree](/refguide/navigation-tree/)

content/en/docs/refguide/modeling/app-explorer/app/navigation/setting-up-the-navigation-structure.md

@@ -8,7 +8,7 @@ aliases:
 ---
 ## Introduction
 
-Once your app has some pages, create a navigation menu to give your users access to them. The navigation editor allows you define the navigation menu for different type of apps and devices (for example, for responsive, tablet browser, or native mobile apps). It also allows you to define which page is shown as a default home page depending on the user role.
+Once your app has some pages, create a navigation menu to give your users access to them. The navigation editor allows you define the navigation menu for different type of apps and devices (for example, for responsive, tablet browser, native mobile, or embedded apps). It also allows you to define which page is shown as a default home page depending on the user role.
 
 ## Setting a Default Home Page {#home}
 
@@ -35,6 +35,8 @@ Do the following:
 For online profiles, you can set a microflow as a default home page. Make sure a [Show Page](/refguide/show-page/) activity is called from the startup microflow for each possible execution flow. Otherwise, the user will see nothing during execution paths where the activity is missing.
 
 For the native mobile profile, you can set a nanoflow as a home page, either as a default or as a role-based. For more information, see the [Setting a Nanoflow as a Home Page](#nanoflow-home-page) section below.
+
+For the Embedded profile, the selected home page is the first page shown when the host application calls `render(...)`. When that page requires parameters, the host application passes them through the `parameters` object in `render(...)`. For more information, see [Embedding the Client](/refguide/mendix-client/embedding-the-client/).
 {{% /alert %}}
 
 Now every time a user signs in to the application, the selected page/microflow is shown/triggered.
@@ -74,6 +76,12 @@ If a microflow is used as a fallback, it can have only one String parameter name
 
 The fallback page will only be used for URLs that start with a [URL Prefix](/refguide/runtime-tab/#url-prefix).
 
+## Setting an Error Page for an Embedded Profile
+
+The Embedded profile can use an error page when the configured home page cannot be opened during startup or navigation. This can happen when the values passed in `render(...)` do not match the expected page parameter types or when the signed-in user does not have access to the configured home page.
+
+To configure an error page, open the Embedded profile in the **Navigation** editor and select the page you want to use.
+
 ## Setting a Nanoflow as a Home Page {#nanoflow-home-page}
 
 Instead of using a page, you can set a nanoflow as your app's home page as long as you are using a native profile. The nanoflow you selected will be executed during startup and will show your app's starting page. This is a normal nanoflow call, which means that you can implement custom logic that determines which page to show, creates objects, calls sub-nanoflows, uses JavaScript actions, and more.
@@ -134,3 +142,4 @@ To avoid adding the menu widget on every page in your app, you can use a layout.
 
 * [Atlas UI](/howto/front-end/atlas-ui/)
 * [Create Your First Two Overview and Detail Pages](/howto/front-end/create-your-first-two-overview-and-detail-pages/)
+* [Embedding the Client](/refguide/mendix-client/embedding-the-client/)