Free cookie consent management tool by TermsFeed Portal Publishing Manager [Appian Portals]
Portal Publishing Manager
The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply.


The Portal Publishing Manager is an application that allows you to manage your portals.

In the Portal Publishing Manager, you can do four main actions:

While you're creating or updating a portal in the Portal Publishing Manager, you can:

Portal details

The portal details section contains essential information about your portal.

Field Description More Information
Portal Name A name to identify your portal. The live Portal URL will contain this name, so use hyphens (-) or underscores (_) instead of spaces. Portal names must be unique.
Interface An interface published in the Portal. Only interfaces which exist in the Appian Designer and are visible to the current user are available to select.
Display Name The name that appears on the browser tab next to the favicon. Display names do not need to be unique.
Application Properties Data Information that allows the Appian Portal to communicate with any data source connected system or integration that you have set up. This is where you upload an import customization file. This information will be stored encrypted.

Google reCAPTCHA

reCAPTCHA is a feature that allows you to monitor your Portals for any potentially malicious or fraudulent activity. Appian works with Google’s reCAPTCHA services to provide you with a configurable experience that allows you to choose your thresholds for and responses to any potential misuses of your Portal.

Before you can add reCAPTCHA to your Portal, you’ll need to get reCAPTCHA keys from Google in the Google Admin Console.

Click Use Google reCAPTCHA to protect your page, to see the following reCAPTCHA setup fields.

Field Description More Information
reCAPTCHA Site Key The reCAPTCHA site key provided by Google. Allows you to use reCAPTCHA on your Portal.
reCAPTCHA API Key The reCAPTCHA secret key provided by Google. Allows your Portal to communicate with the Google reCAPTCHA server.
reCAPTCHA Project ID The reCAPTCHA project ID provided by Google when you create a project. Allows your Portal reCAPTCHA to be associated with the right project in the Google Admin Console.

For steps on adding reCAPTCHA, see Publish a Portal.

For more reCAPTCHA guidance or further information on setting up and using reCAPTCHA, check out Configuring reCAPTCHA.


The Branding section lets you configure the following fields to ensure that your Portal matches your branding and style requirements.

Field Description Default
Favicon Image The favicon (or "favorite icon") is the icon that appears in the browser tab or URL bar. File must be type .ICO with 16x16 and 32x32 sizes. Appian favicon
Input Shape The shape applied to all input fields and selection fields in the Portal. There are two options for input shape: squared and semi-rounded. Squared
Button Shape The shape applied to all buttons in the Portal. There are three options for button shape: squared, semi-rounded, and rounded. Squared
Accent Color Affects the color of many elements in the Portal, such as buttons, links, active field border colors, milestone bars, and section titles. #2322F0
Loading Bar Color The color of the bar at the top of the page that indicates when the system is processing. Accent color

For steps on how to configure branding, see Publish a Portal.

For best practices on configuring branding, check out our similar UX guidance for configuring site branding.

Portal branding considerations

  • Portals do not include navigation bars. To get a similar look to the navigation bar, use a header content layout.
  • The page width for a Portal will always be "FULL", regardless of the size of the window. To change the form formatting to fit any window, use responsiveness features like the stackWhen parameter in columns layouts and side by side layouts or the a!isPageWidth() function.


The Security section allows you to add any service accounts and credentials that you need to link to your portal.

Service accounts are the main way that you manage end user security for your portal. A service account is a set of credentials that serves as a stand-in Appian user account and uses an API key or Appian credentials to allow your end-users to do the following actions in your portal:

  • View queried data
  • Submit data
  • Upload documents
  • Download documents
  • View document images

For steps on adding a service account, see Publish a Portal.

For more information about service accounts, check out our guidance on using service accounts in your portal.

Open in Github Built: Thu, May 23, 2024 (08:46:51 PM)

Portal Publishing Manager