# Configure the platform experience You can configure settings for the overall platform experience using the **Platform experience** page in Control Panel. To view the **Platform experience** tab, you must have one of the following roles: * **Enrollment administrator** granted in the **Enrollment permissions** extension. * **Organization administrator** or **User experience administrator** granted in the **Organization permissions** extension. ## Configure the home page URL An Organization's home page URL can be configured per Organization or per user group in the **Platform experience** tab of Control Panel. ![Configure the home page URL in the Platform experience settings.](../../../assets/a9b2182ffb7498a6ac6a901cce751846764871e1e9e65191858104592fbb0f04.webp) Examples of some common setups: * Most new Foundry enrollments will display a default narrative home page that helps users learn about the Foundry platform. The URL of this home page is `/narrative`. * If a [Slate](../../slate/overview/index.md) dashboard should be used as the Organization's home page, set the value to `/slate/`. * If a [Carbon](../../carbon/overview/index.md) workspace should be used as the Organization's home page, set the value to `/carbon/` If certain user groups should be sent to a home page URL that differs from the Organization default, you can add group-specific overrides under **Group override** from the left sidebar. The first entry in that list, where a user is a member of any of the listed groups, will be used. ## Configure available languages You can make additional languages besides English available to your users from the **Platform experience** extension. ![Configure languages in the Platform experience settings.](../../../assets/a3a6f88bc34d764af7b415c233b5ae982b24563c13803d6f6f4cd4ea1de89cc0.webp) Users who have access to additional languages will see a locale switcher in their Foundry sidebar that enables language selection. If the **Respect user's browser language preferences** or **Always use browser's language preferences when localizing values** options are enabled, users will initially see Foundry in the available language that is set as highest priority in their web browser preferences. Otherwise, English is used by default until the user selects a different language from the language switcher. :::callout{theme="neutral"} Certain widgets in Foundry are set to the user's browser language preference and may require the browser language setting to be updated where necessary. ::: ## Configure the platform logo The platform logo can be configured per Enrollment and Organization, replacing any occurrences of the default Palantir logo with an image of your choice. Configuring logos per Enrollment requires **Enrollment administrator** permissions. Without those permissions, you can configure logos only per Organization. You can provide up to four different logo sizes: favicon, small, medium, and large. If you do not provide an image for each size, then Foundry uses an appropriate fallback size. The favicon does not have any fallback behavior. When customizing your logo, you should upload a favicon and *at least* one of the other three sizes. | Size | Fallback | | ------- | ------------- | | Favicon | (none) | | Small | Medium, Large | | Medium | Small, Large | | Large | Medium, Small | ![Configure the platform logo in Platform experience settings.](../../../assets/25b5148f133863fa7f1608796ccc8af334ac9c7f8834da2ffa83bacb1da1dd75.webp) ## Configure the platform title The platform title can be configured per Enrollment and Organization and replaces references to the platform with the provided title. Configuring the title per Enrollment requires **Enrollment administrator** permissions. Without those permissions, you can configure the title only per Organization. The default platform title is `Palantir`. You can configure this in the **Platform title** tab of the **Platform experience** extension. Once you configure a new platform title, this update will also be reflected in the name of your in-platform documentation. For example, if you rename your platform to `ABC`, the in-platform documentation application will change from the default `Custom documentation` title to `ABC documentation`. ![Configure the title of your platform in the Platform experience settings.](../../../assets/6a2bd96c3fef17e1dec3a98ac173c7c089aae54c1822592f64044fdbf124ce48.webp) ## Configure platform version The [platform version switcher](index.md#platform-version-switcher) lets you choose between using different versions of the platform. For instance, some users may prefer to use the *beta* version of the platform to access new features earlier, before they are available on the *stable* version of the platform. To view and configure the **Platform version** tab in Control Panel, a user needs the **Manage platform version** workflow, which is granted by the **User experience administrator** role. Roles are administered in the **[Organization permissions](../enrollments-and-organizations-permissions/index.md#roles)** tab in Control Panel. ### Platform versions There are three platform versions available through the platform version switcher: [stable](#stable), [beta](#beta), and [prior](#prior). #### Stable The stable release has been rigorously tested and has widespread usage. The vast majority of users will be using the stable release. #### Beta The beta release is a future stable release that contains new changes and features not yet available on the current stable release. Because the beta release is newer, the changes made in this release may not be as rigorously tested as the stable release, and you may encounter unexpected behaviors. When building in the Palantir platform, opting into the beta release can be useful to get access to features early. #### Prior The prior release is the stable release that existed immediately previous to the current stable release. Switching to the prior release can be useful for viewing the old UI in case of changes made in the stable release, but the prior release is not recommended for everyday use. Users can temporarily view the prior version, but will be automatically moved back onto their default version (see [Configuring users' default platform version](index.md#configuring-users-default-platform-version)). ### Platform version switcher To change the platform version, navigate to account settings in the bottom of the left sidebar, then select the current version next to **Platform version** to open the platform version switcher. Choosing a different version will reload the page and load the new version. Change platform version. The default version shown to users is determined by the [default platform version setting in Control Panel](index.md#configuring-users-default-platform-version). When viewing a platform version other than the stable release, a small tag will be visible in the sidebar to indicate that the user is viewing a different release. Platform version tag visible in sidebar. ### Restricting access to the platform version switcher Access to the platform version switcher in the sidebar can be restricted for users in your organization. To change access to the switcher, navigate to the **Platform experience** extension, then go to the **Platform version** tab. ![Platform version tab](../../../assets/1cf0370cfe10f38b2097139144707f5038928dd2096a41254bf8ee6d5fedda8b.webp) Select **Manage** next to **Platform version switcher** to bring up a dialog to change the platform version switcher setting. ![Platform version switcher dialog](../../../assets/5c03bf71b61a1d909c20ca57ce58c1ddf4326f2b9646b072409684cdefcc6306.webp) Select the desired access, then select **Request and apply change for your organization**. This will create a change request in the [Approvals inbox in Control Panel](../control-panel-approvals/index.md) that will automatically be self-approved and applied. To view all past changes, choose **Platform version switcher requests** in the approvals inbox. ![Platform version switcher request](../../../assets/8a08e787929433c34eac5c00b2051a96b1dca623af61875b258940f4465b017b.webp) ### Configuring users' default platform version Administrators can additionally configure groups of users to use the beta platform version by default. If any of these users have access to the platform version switcher, they will still be able to switch to a different version from the beta version. This enables you to select a group of power users that should use the beta version by default, so that they can try new features out before the rest of your users see them. ![Platform version default](../../../assets/1dfcce924082c28da560888eced333a1791e0c7b5d2d2147936d2e42409773a5.webp) To configure which users should see the beta version by default, select **Manage** next to **Default platform version**. In the dialog, select the desired groups to use the beta version; any users not in the selected groups will see the stable version by default. ![Platform version default dialog](../../../assets/c2b1968b90619357424986f2b4c106bc79644bb813be0e4c82c4385e912a88f6.webp) When you are done with configuration, select **Request and apply change for your organization**. This will create a change request in the [Approvals inbox in Control Panel](../control-panel-approvals/index.md) that will automatically be self-approved and applied. To view all past changes, choose **Platform version default requests** in the approvals inbox. ![Platform version default request](../../../assets/af6d1a0cd6ed0ead4dd5266317497af860fd47f61eb640a7129a25b2d7bfb7cc.webp) ## Configure the static banner You can configure a static banner per Organization that renders at the top, bottom, or top and bottom of every page. The **Banner text** field supports basic Markdown syntax. This setting is disabled by default. ![Configure the static banner in the Platform experience settings](../../../assets/e7e4c5165a1c40bbbbc823c5261b21223f56c6227df9016ba0bc9adfa4a1b278.webp)