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 User experience administrator Organization permissions.

Configure the home page URL

An Organization's home page URL can be configured per Organization as well as per user group in the Platform experience tab of Control Panel.

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 for this home page is /narrative.
• If a Slate dashboard should be used as the Organization's home page, set the value to /slate/<dashboard-rid-or-permalink>.
• If a Carbon workspace should be used as the Organization's home page, set the value to /carbon/<workspace-rid>

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 the platform title

Your Organization's platform title can be configured per Organization and replaces references to the platform with the provided title. The default platform title is Palantir. You can configure this in the Platform title tab.

Once you configure your platform title to a new name, 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 available languages

You can also make additional languages besides English available to your users from the Platform experience page.

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.

Configure platform version

The 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 tab in Control Panel.

Platform versions

There are three platform versions available through the platform version switcher: stable, beta, and 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).

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.

The default version shown to users is determined by the default platform version setting in Control Panel. 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.

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.

While this feature is in beta, no users will have default access to the platform version switcher. However, when the switcher is made generally available, organizations that have not made any changes to their switcher access settings will have access to the platform version switcher automatically enabled for everyone in an organization by default. If some users should not have access to the platform version switcher, you must make a change to the initial access settings such that those users will not automatically receive access.

Select Manage next to Platform version switcher to bring up a dialog to change the platform version switcher setting.

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 that will automatically be self-approved and applied. To view all past changes, choose Platform version switcher requests in the approvals inbox.

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.

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.

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 that will automatically be self-approved and applied. To view all past changes, choose Platform version default requests in the approvals inbox.