Appian Portals

As per Appian documentation - docs.appian.com/.../portals-home.html

Portals are great if your use cases are:

• Public and unauthenticated: You want to share information with or collect data from public users who don't need to sign in.
• Connected to Appian: You want external users to be able to kick off Appian workflows or see information that comes from your Appian environment.
• Easily secured: You need your implementation to be SOC 2 or HIPAA compliant and you want to take advantage of security benefits like reCAPTCHA.

And Portals should not be used for:

• Account-level access: Your users need to view multiple cases, records, or workflows associated directly to them. For example, accessing their plan and billing with a utility company, like seeing a history of service appointments and past bills paid. If they have that amount of information to manage, it's best to have them log into a user account.
• Marketing-focused websites: You require pixel-perfect control, cookies, or need to integrate with tracking and web analytics services.
• Shopping cart/commerce: For example, an online shopping website. These websites generally require things such as cookies to allow users to do something like refresh their page and keep the items in their shopping cart.

As per Appian documentation - docs.appian.com/.../portals-home.html

Portals are great if your use cases are:

• Public and unauthenticated: You want to share information with or collect data from public users who don't need to sign in.
• Connected to Appian: You want external users to be able to kick off Appian workflows or see information that comes from your Appian environment.
• Easily secured: You need your implementation to be SOC 2 or HIPAA compliant and you want to take advantage of security benefits like reCAPTCHA.

And Portals should not be used for:

• Account-level access: Your users need to view multiple cases, records, or workflows associated directly to them. For example, accessing their plan and billing with a utility company, like seeing a history of service appointments and past bills paid. If they have that amount of information to manage, it's best to have them log into a user account.
• Marketing-focused websites: You require pixel-perfect control, cookies, or need to integrate with tracking and web analytics services.
• Shopping cart/commerce: For example, an online shopping website. These websites generally require things such as cookies to allow users to do something like refresh their page and keep the items in their shopping cart.