Overview

Appian allows you to view and create four types of folders: rule folders, process model folders, knowledge centers, and document folders. This page explains how to create and manage these types of folders (as well as documents in document folders) within your applications.

Managing folders

In Appian, you can create, update, and delete folders and their contents in Appian Designer or an application view. In addition, knowledge centers and document folders can be managed through a variety of Document Management smart services.

Creating folders

To create a new folder of any type:

1. In the application view, click New > Folder.

   

2. Configure the following properties:

   Property	Description
   Type	Select the type of folder you want to create: Rule Folder Process Model Folder Document Folder Knowledge Center
   Folder Name	Enter a name that follows the recommended naming standard.
   Folder Description	(Optional) Enter a description for the folder.
   Parent Folder	(Required for document folders) Select a parent folder. By default, child folders inherit security from the parent folder.

3. Click CREATE.

   

4. Configure the folder security.
5. Click SAVE.

Deleting folders

Folders can be deleted by users with Administrator permission to them.

To delete a folder:

1. Go to an application that contains the folder.

   If you are a Basic user, the folder must be empty before you can delete it.

2. Select the folder in the grid and click the Delete button in the grid toolbar.

   System Administrators can delete folders (and other objects) in bulk by selecting them and clicking Delete in the toolbar. In this case, folder contents will automatically be deleted when the folder is deleted.

Viewing and modifying folder contents and properties

In the objects and application views, you can search or filter for folders. Another quick way to find a top-level folder is to switch to the hierarchical view.

To see the contents of a folder, click on the folder name.

The annotated image above shows a folder view.

1. Breadcrumbs: Display the folder hierarchy (including all parent folders of the current folder) and allow developers to navigate between folders and subfolders. Click on any folder name within the breadcrumbs to navigate to it.
2. Gear menu: Provides developers with relevant actions which can be taken on the current folder, including viewing and editing the folder's Properties, Security settings, or location. In the example below, any selected gear menu action will be applied to the VM Category Icons folder.
3. New button: Allows developers to create new objects within the current folder. The type of objects you can create depends on the type of folder you're viewing.
4. Toolbar: Allows developers to take actions on selected objects located within the current folder.
   • Move button: Allows developers to move selected objects between folders.

Setting and editing folder security

Folder security determines which groups can access and modify a folder, its properties, and any objects within it that inherit security.

Developers can set and edit folder security in either of the following ways:

• In the objects view or the application view, select a folder, then click the SECURITY toolbar button.
• In a folder view, click , then select Security in the dropdown list.

Learn more about editing folder security.

Learn more about the different security settings for each folder type in the following sections:

• Rule folder security
• Process model folder security
• Knowledge center security
• Document folder security

Rule folders

Rule folders can only contain the following object types:

• Interfaces
• Expression Rules
• Decisions
• Constants
• Integrations
• Other rule subfolders

Rule folder security

The security role map of a rule folder controls which users can see or modify it, its properties, and its contents that inherit security.

If default security groups are configured for your application, the default security groups pre-populate the role map when you create a rule folder. If default security groups are not configured for your application, you are automatically assigned Administrator permissions for any rule folder you create. System administrators can always access a rule folder, regardless of object-level permissions.

See Editing Object Security to modify a rule folder's security.

The following table outlines the actions that can be completed for each permission level in a rule folder's security role map. This table assumes that objects within the rule folder inherit security (default). If an object does not inherit the folder's security, then the object's individual security role map applies.

Actions	Administrator	Editor	Viewer	Deny
View the rule folder	Yes	Yes	Yes	No
Create objects in the rule folder	Yes	Yes	No	No
View the security	Yes	Yes	No	No
Update the security	Yes	No	No	No
Delete the rule folder	Yes	No	No	No

Process model folders

Process model folders can only contain process models and process model subfolders.

Process model folder security

The security role map of a process model folder controls which users can see or modify it and its properties.

If default security groups are configured for your application, the default security groups pre-populate the role map when you create a process model folder. If default security groups are not configured for your application, you are automatically assigned Administrator permissions for any process model folder you create. System administrators can always access a process model folder, regardless of object-level permissions.

See Editing Object Security to modify a process model folder's security.

The following table outlines the actions that can be completed for each permission level in a process model folder's security role map. This table only applies to the security of process model folders. Process models within the folder have individual security role maps.

Actions	Administrator	Editor	Viewer	Deny
View the process model folder	Yes	Yes	Yes	No
Create objects in the process model folder	Yes	Yes	No	No
View the security	Yes	No	No	No
Update the security	Yes	No	No	No
Delete the process model folder	Yes	No	No	No

Knowledge centers

Knowledge centers are containers for folders and their files. They can contain only document folders and documents. The System and Temporary Documents Knowledge Centers are system knowledge centers available by default in Appian Designer.

System knowledge center

The System Knowledge Center is used to store system documents, including:

• Email headers and footers
• Priority icons
• System reports
• User pictures

By default, all users have Viewer permission to this knowledge center.

Temporary documents knowledge center

The Temporary Documents knowledge center is used to store system and process objects in transition. Files that are uploaded using the file upload component are temporarily stored in this knowledge center, but they cannot be accessed or viewed from the user interface.

By default, all users have Editor permission to this knowledge center.

Knowledge center security

The security role map of a knowledge center controls which users can see or modify it, its properties, and its contents.

If a knowledge center has a parent community (a deprecated folder object), it inherits the community's security. If the security of the community and the knowledge center conflict, the community's security takes precedence.

For all other knowledge centers, you can configure the security for the knowledge center during creation and any time after that. If default security groups are configured for your application, the default security groups pre-populate the role map when you create a knowledge center. If default security groups are not configured for your application, you are automatically assigned Administrator permissions for any knowledge center you create. System administrators can always access a knowledge center, regardless of object-level permissions.

See Editing Object Security to modify a knowledge center's security.

The following table outlines the actions that can be completed for each permission level in a knowledge center's security role map. This table assumes that objects within the knowledge center inherit security (default). If an object does not inherit the knowledge center's security, then the object's individual security role map applies.

Actions	Administrator	Editor	Viewer	Deny
View the knowledge center	Yes	Yes	Yes	No
Create new documents or move documents into a subfolder under the knowledge center (must have at least Editor permissions to the subfolder)	Yes	Yes	Yes	No
Create new subfolders in the knowledge center	Yes	Yes	No	No
View the security	Yes	Yes	No	No
Update the security	Yes	No	No	No
Move and delete subfolders	Yes	No	No	No
Move and delete the knowledge center	Yes	No	No	No

Knowledge center security can also be updated using the Modify KC Security Smart Service. Note that the security permission levels Author and Reader in the smart service correspond to Editor and Viewer respectively.

Document folders

Document folders can contain subfolders and documents, and must reside in a parent folder or knowledge center.

Document folder security

The security role map of a document folder controls which users can see or modify it, its properties, and its contents.

By default, document folders inherit security from their parent knowledge center. However, after creating the document folder, you can disable that inheritance and modify the folder's security. See Editing Object Security to modify a document folder's security.

The following table outlines the actions that can be completed for each permission level in a document folder's security role map.

Actions	Administrator	Editor	Viewer	Deny
View the document folder	Yes	Yes	Yes	No
View and download documents that reside in the document folder	Yes	Yes	Yes	No
Update documents that reside in the document folder	Yes	Yes	No	No
Create new subfolders and documents in the document folder *	Yes	Yes	No	No
View the security	Yes	Yes	No	No
Update the security	Yes	No	No	No
Move subfolders or documents into the document folder *	Yes	No	No	No
View download metrics for documents that reside in the document folder	Yes	No	No	No
Move documents out of the document folder	Yes	No	No	No
Move and delete the document folder	Yes	No	No	No

Managing documents

A document object is any file of any file type that you upload to Appian. All documents must be saved in document folders. They cannot be saved directly into knowledge centers.

Documents can be managed in Appian Designer and through a variety of Document Management smart services. This page focuses on managing documents within Appian Designer.

Creating documents

There are multiple ways to create new documents, including:

• In the application view
• In a document folder view
• In the Application Documentation dialog
• Uploading on an interface with a!fileUploadField()
• Using a Document Generation smart service
• Receiving a binary or Base64 document through an integration
• From a robotic task using document actions

In Appian Designer, you can create new documents (up to 25 at a time) or upload zip files.

To create a new document:

1. From the application view or document folder view, click New > Document.
2. Upload up to 25 files.
   • Files cannot be larger than your disk quota.
   • Files cannot be larger than 1GB in size.
3. Click NEXT.

4. Configure the following properties:

   Property	Description
   Save In	Browse to and select an existing folder or create a new folder to store the document object.
   Name	For each file you uploaded, enter a name that follows the recommended naming standard.
   Description	(Optional) For each file you uploaded, enter a brief description of the file.
   Create constants for these documents	Select the checkbox to enable this option. When enabled, Appian will create one constant per file. Constants will be added to your current application and its corresponding rule folder. If your application does not contain a rule folder, Appian will automatically create a rule folder and add the constants to it.

5. Click CREATE DOCUMENT.

   

Document security

Documents always inherit security from their parent folder.

See document folder security to learn more about the permission levels required for creating, editing, and downloading documents.

Adding new document versions

Once a document has been created, new versions of it can be uploaded at any time. See Managing Object Versions to learn more about viewing and comparing document versions.

To upload a new version of a document:

1. From the application view, select the document.
2. Click More and select the New Version option.
3. Select the new version of the file from your local machine.
4. You can keep the file name listed in the Name field, or modify it as needed. The file name must be at least four characters long.

   The file extension of the newly uploaded document must match the file extension of the originally uploaded file.

5. (Optional) Edit the description of the file. The description can be viewed in the document properties.
6. Click Upload.

Viewing document properties

To view a document's properties you must have at least Viewer permissions to the document and its parent folder. To edit a document's properties you must have at least Editor permissions to the document and its parent folder.

To view or edit a document's properties:

1. From Appian Designer or the application view, select the folder or document.
2. Click More and select the Properties option.

Deleting documents

A user must have Administrator permissions to the document and its folder in order to delete it. Deleting a document removes the specific file and all of its previous versions.

To delete a document:

1. Select the document in Appian Designer or the application view.
2. Click Delete.
3. Confirm that the document has no dependents and click Delete again.

Document hierarchies

Moving documents and folders in your document hierarchy

You can move folders or documents within knowledge centers or other folders if you have Administrator permissions to the source parent folder and at least Editor permissions to the destination parent folder or knowledge center.

To move a folder or document:

1. Select the folder or document in Appian Designer, the application view, or the document folder view.
2. Select the Move button on the toolbar.
3. Select the Destination knowledge center or folder.
4. Click Move.

Downloading document hierarchies

You can download the contents of entire knowledge centers and folders if you have at least Viewer permissions to them.

You can download document hierarchies in two ways:

1. From within Appian Designer or an application view, select the knowledge centers, folders, or documents you want to download, click the More toolbar button, and select Download.
2. From within a folder view, click on the gear menu next to the folder name and select Download in the dropdown.

Uploading document hierarchies into Appian

The document folder view in Appian designer allows you to upload a ZIP file of a document hierarchy. Uploading this zip will create document folders and documents in Appian in the exact structure as the folders and files are inside the ZIP. This is useful when you need to create many documents at once or have a folder structure you want to bring into Appian.

You must have at least Editor permissions to the document folder in order to upload a ZIP. You must also have at least Viewer permissions to all of the folders and knowledge centers that the document folder resides in.

To upload a document hierarchy:

1. Compress your files into a ZIP format archive.
2. Navigate to the document folder that you'd like this hierarchy to be created in.
3. Click Upload ZIP.
4. Select the ZIP archive from your computer. Click Upload.

Managing process reports

Process reports are stored as documents in Appian, as Appian Report Files (.arf). They can be created, edited, and moved between document folders just like document objects.

Managing application documentation

Appian stores application documentation as document objects. You can manage your newly uploaded document directly from within the Application Documentation dialog, or from the application view.

You must remove the document object from the documentation list before you try to delete the document object or remove the document object from the application. Otherwise, Appian will block the action.