Secure Your Data Fabric

Enterprise data often includes information that must be protected for business, privacy, or regulatory reasons. Appian's data fabric provides multiple layers of security to ensure the right users see the right data. This page explains how those layers work together and where to start.

How security layers work together

Record type security is applied in layers, from broadest to most granular. Each layer builds on the one above it:

Layer	What it controls	Example
Object security	Who can view or modify the record type itself	Only the HR team can edit the Employee record type.
Record-level security	Which rows of data each user can see	Support engineers only see their assigned cases.
Field-level security	Which fields each user can see	Only HR can see the social security number field.
Record view security	Which record views each user can see	Only managers see the Performance view.
Record action security	Which record actions each user can see	Only admins can delete an employee.

Appian automatically enforces your security configurations anywhere the record type is used, including record lists, queries, grids, charts, and related record data.

Where to start

Every record type needs object security configured. This is the broadest layer and determines who can access the record type at all.

From there, add more granular layers based on your business requirements:

• If different users should see different subsets of records, configure record-level security.
• If certain fields contain sensitive data, configure field-level security.
• If certain views or actions should only be available to specific users, configure record view security or record action security.

Workspace settings

Workspace settings determine whether the record type appears as a dataset in Process HQ or as a record in Tempo. While not strictly a security feature, workspace settings control the visibility of your record type in end-user workspaces.

Feedback