|The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply.
Appian Portals is the front door to your Appian applications. It connects external users to the information and processes that you already have in Appian. With Appian Portals, you can use low-code to build public websites that are conveniently connected to your Appian applications.
Public users can use portals to submit forms, file claims, view documents and information, and more. All without requiring them to log in.
Appian Portals is currently only supported for Appian Cloud customers. Additionally, if your environment is behind a VPN, you cannot connect a portal to it to read or write data.
One of the main benefits of Appian Portals is that you can use a single platform to build both the external and internal sides of your applications. But the advantages don't stop there. Below are some of the most enticing reasons organizations choose to adopt Appian Portals.
With Appian Portals, you can use the same low-code tools you already know to quickly design, create, and manage websites. Create an interface using all the dynamism and speed that you expect from Appian, then simply publish it publicly using the Portal Publication Manager.
No need to worry about hosting and scaling these sites on your own. Appian Portals eliminates the unpredictable costs and oversight that comes with traditional infrastructure alternatives.
Because portals are an extension of the Appian Low-Code platform, you can expect the same level of security, including encryption, SOC 2 compliance, and more.
Additionally, you can use reCAPTCHA to monitor your portals for potentially malicious or fraudulent activity.
Appian has always been great at managing your internal workflows. Appian users experience the benefits of their Appian applications every day. They have access to the important information and workflows they need to perform their daily tasks.
Public users are different. You don't want to expose sensitive or non-public information to them. But you may want to show them information that you already have in Appian. For example, a power utility may use Appian to track outages. They can use the information that's already in Appian to create a public portal that has an outage dashboard.
A portal simply connects external users to the information in Appian applications that is relevant to them, easily and securely.
There are many use cases that are a perfect fit for a portal. If you want to connect your external users to your Appian data and workflow, a portal will likely be a great choice.
Portals are great if your use cases are:
The following are great use cases for a portal:
There are some use cases that are a better fit for other tools. For example, you're probably not going to want to build your organization's main website as a portal. But you could build a smaller website and link to it from your navigation menu.
Portals aren't the best fit if your use cases are for:
GovCloud customers can still use Appian Portals even though it isn't FedRAMP certified yet. Publishing a portal uses an external connection to the Appian Portals service. This connection requires the same ATO process as any other external connection, such as connecting to an Oracle database.
Portals don't typically store data. To guarantee your portals don't store data outside your GovCloud environment, reference documents by IDs, not constants.
The following use cases would not be great for a portal: