Abstract: A system and method of an in-place content management system that allows an organization to bring the power of an enterprise content management (ECM) system (supporting such features as check-out, check-in, security, audit, add, rename, move, delete, classification, legal holds and disposition) to the data where it resides on an NTFS file system, eliminating the need to move it somewhere else and without having to change the way end-users work. A utility or tool for content management that leverages the existing security that is already in place on files and folders and adds basic content management features such as check-out/check-in (preventing multiple users from editing the same document at the same time), audit history, and the ability to add classifications, trigger dispositions, and apply legal holds on documents where they currently reside.

Abstract: A system and method of dynamic search result permission checking. A system that provides end users the ability to search an index (i.e., Shinydocs Index) built from content from one or multiple source repositories, and only display results for which the user has sufficient permissions at source to view. User credentials are validated “on the fly”, such that these checks are performant across a multiple of possible back-end repositories sequentially or simultaneously. The resultant search results from the Index may be sourced from many disparate repositories, each of which have their own unique permission structure (to view individual items). A method for handling permissions in multiple repositories in a secure (yet performant) fashion in order to only display search results that the end-user is allowed to view based on source system permissions.

Abstract: A system and method of dynamic search result permission checking. A system that provides end users the ability to search an index (i.e., Shinydocs Index) built from content from one or multiple source repositories, and only display results for which the user has sufficient permissions at source to view. User credentials are validated “on the fly”, such that these checks are performant across a multiple of possible back-end repositories sequentially or simultaneously. The resultant search results from the Index may be sourced from many disparate repositories, each of which have their own unique permission structure (to view individual items). A method for handling permissions in multiple repositories in a secure (yet performant) fashion in order to only display search results that the end-user is allowed to view based on source system permissions.