What are permissions in AODocs?

In AODocs, permissions control who can access and modify your documents. They are applied at the document level.

• Each document in a library can have unique permissions.
• Permissions can be set automatically by AODocs rules.
• Users can also add explicit permissions.

What are the types of permissions in AODocs?

There are four kinds of permissions in AODocs:

• Read: the permission to read a document.
• Write: the permission to modify a document.
• Delete: the permission to delete a document.
• Share: the permission to modify a document's access rights.

How does AODocs determine document permissions?

AODocs calculates a document's final permissions based on a combination of rules which are applied in a specific order:

1. Library administrators always have full access (read, write, delete, and share).
2. Inherited permissions: if enabled, the permissions of the document’s “parent object” are applied. Depending on the security configuration of the document class, the document’s “parent object” can be:
   • the document class
   • the document’s parent folder
   • the document’s current workflow state
3. Specific document permissions are applied.

AODocs combines these three rules to determine who can access each document.

Best Practice: We recommend using inherited permissions to set document security. This is generally more efficient than setting permissions on individual documents.

What are inherited permissions?

Inherited permissions let you manage access for many documents with fewer settings. 

AODocs offers three ways to apply inherited permissions:

• Document class permissions: a single set of permissions for all documents within a document class.
• Workflow permissions: document permissions are controlled by the workflow engine.
• Folder permissions: document permissions are determined by the document's parent folder.

Learn more: Set workflow permissions

You can configure inherited permissions in the Security tab of your document class settings.

When should you ignore inherited permissions?

You can configure documents and folders to ignore permissions from their parent object (document class, workflow state, or folder). When you do this, inherited permissions do not apply.

Instead, the document's (or folder's) permissions will be determined by:

• Library administrators (who always have access).
• Specific permissions set directly on that document or folder.

For example, you might use this feature to create "private" folders inside "public" folders.