You are currently reviewing an older revision of this page.

KB-1700 Document security does not update after moving a document


After moving a document to a new folder via Appian Designer or using the Move Document smart service, the document remains inaccessible to users who have "Viewer" privileges or higher to the target folder but no access to the source folder. These users are able to see new documents uploaded to the target folder as expected.


When viewing the security of the document itself, the security matches the target folder's security as intended.


This is a known issue in which document security does not update correctly after moving a document. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-79520.


If the issue is encountered when moving documents using Appian Designer, consider using a process model with the workaround below.

Include an Inherit Security from Parent for Document smart service node, provided by the Content Security Utilities Shared Component, after the Move Document node in the impacted process models. The smart service will force the content security to refresh after it has been moved.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018