US-12619785-B2 - Systems and methods for document hierarchy permissioning

Abstract

Provided herein are systems, methods, and computer readable media for document hierarchy permissions. This may include providing a permission database comprising a plurality of users, a plurality of advisors, and a plurality of categories. A candidate document is received at a network device. A candidate user, a candidate routing action, and a candidate document category are identified from the candidate document. A candidate document permission attribute is generated identifying the candidate user, candidate file location, and the candidate document category. The candidate document is stored, and the candidate document permission attribute corresponding to the candidate document is stored.

Inventors

• Luke Joseph Kyleman
• Ka Fu Ko

Assignees

• FutureVault Inc.

Dates

Publication Date

20260505

Application Date

20220725

Claims (18)

1. 1 . A system for determining the permissions of an electronic file, the system comprising: a memory, the memory comprising: a permissions database, the permissions database comprising a plurality of users, a plurality of advisors, and a plurality of categories; a network device for receiving a candidate document; a storage system for storing documents; a processor in communication with the memory, the network device, and the storage system, the processor configured to: identify from the candidate document a candidate user in the plurality of users, a candidate document routing action, and a candidate document category in the plurality of document categories, wherein the candidate user is identified based on an electronic signature or an XML element determined from the candidate document, and wherein the candidate document routing action comprises a matching routing criteria; evaluate metadata of the candidate document using the matching routing criteria; responsive to the metadata of the candidate document matching the matching routing criteria, execute the candidate document routing action; generate a candidate document permission attribute based on the candidate document in the permissions database, the candidate document permission attribute identifying the candidate user, a candidate file location based on the candidate document routing action, and the candidate document category; store, in the storage system, the candidate document; and store, in the memory, the candidate document permission attribute corresponding to the candidate document in the permissions database.
2. 2 . The system of claim 1 , wherein the processor is further configured to: assign a category permission to an advisor in the plurality of advisors, the category permission corresponding to a first document category in the plurality of categories.
3. 3 . The system of claim 2 further comprising: a display device in communication with the processor, the display device for displaying the candidate document; and wherein the processor is further configured to display the candidate document at the display device when the candidate document category matches the category permission of the candidate advisor.
4. 4 . The system of claim 1 , wherein the candidate document category is determined based on a classification from a machine learning model.
5. 5 . The system of claim 1 , wherein the candidate document category is determined based on a rule-based category model.
6. 6 . The system of claim 1 , wherein the candidate document routing action comprises a candidate organization of the candidate document.
7. 7 . The system of claim 1 , wherein the candidate document category further comprises a category identifier and a sub-category identifier.
8. 8 . The system of claim 1 , wherein the category identifier and the sub-category-identifier define the candidate file location within a file hierarchy.
9. 9 . The system of claim 1 , wherein the candidate document has a metadata item associated therewith, and the generating the candidate document category is based on the candidate document and the metadata item.
10. 10 . The system of claim 1 , wherein the candidate file location of each document permission comprises a first level file location in a hierarchy of file locations.
11. 11 . The system of claim 1 , wherein the candidate file location of each document permission comprises a second level file location in a hierarchy of file locations.
12. 12 . The system of claim 1 , wherein the identifying the candidate user further comprises identifying the candidate user based on an email address determined from the candidate document.
13. 13 . The system of claim 1 , wherein the identifying the candidate user further comprises: determining, at the processor, that the candidate user identified is a low-confidence match; and wherein the candidate document permission for the low-confidence match comprises a temporary storage for the candidate document.
14. 14 . The system of claim 1 , further comprising: a user input device in communication with the processor for receiving a user input corresponding to the candidate document in the temporary storage; wherein the processor is further configured to generate a user generated candidate document permission attribute based on the user input.
15. 15 . The system of claim 1 , wherein the processor is further configured to: determine that the candidate user does not correspond to a candidate user record in the permissions database; and generate a file storage vault for the candidate user, and a corresponding candidate user record for the candidate user.
16. 16 . The system of claim 1 , wherein the candidate document is received at the network device via an Application Programming Interface (API).
17. 17 . A method for determining the permissions of an electronic file, the method comprising: providing, at a memory in communication with a processor, a permissions database, the permissions database comprising a plurality of users, a plurality of advisors, and a plurality of categories; receiving, at a network device in communication with the processor, a candidate document; identifying from the candidate document, at the processor, a candidate user in the plurality of users, a candidate document routing action, and a candidate document category in the plurality of document categories; generating, at the processor, a candidate document permission attribute based on the candidate document in the permissions database, the candidate document permission attribute identifying the candidate user, a candidate file location based on the candidate document routing action, and the candidate document category, wherein the candidate user is identified based on an electronic signature or an XML element determined from the candidate document, and wherein the candidate document routing action comprises a matching routing criteria; evaluating metadata of the candidate document using the matching routing criteria; responsive to the metadata of the candidate document matching the matching routing criteria, executing the candidate document routing action; storing, in a storage system, the candidate document; and storing, in the memory, the candidate document permission attribute corresponding to the candidate document in the permissions database.
18. 18 . A non-transitory computer-readable medium with instructions stored thereon for determining the permissions of an electronic file, that when executed by a processor, performs the method of claim 17 .

Description

CROSS-REFERENCE TO RELATED APPLICATION This application claims the benefit of U.S. Provisional Patent Application No. 63/225,659, filed Jul. 26, 2021, the entire content of which is incorporated herein by this reference. FIELD The described embodiments relate to electronic document management, and in particular systems, methods and computer readable media for assigning permissions to documents in a database. BACKGROUND People often use filing cabinets and file folders to store important documents. To make these filing systems useful, the folders and documents are generally organized and managed to make document retrieval convenient and easy. With electronic documents, databases with folder structures can be used to store documents. As with physical documents, organizing and managing the database aids in making documents easily retrievable. Managing electronic documents further introduces challenges of setting appropriate document permissions so that documents may be shared between users, and other trusted individuals such as trusted advisors. Managing electronic document databases can be a tedious and time-consuming task. Because electronic documents are easy to create and disseminate, large numbers of documents may be filed in electronic databases. The increased number of documents often results in an increased number of file folders and potential file locations, and makes it difficult to automatically determine document permissions for sharing. As a result, individuals may neglect to share their documents, resulting in problems with shared documents that may be provided to associated users such as advisors. This may mean that an advisor user has to manually remind another user to share a particular document. Another difficulty when managing electronic databases is that the documents may be created without predefined permission categories. For instance, document management systems, scanners and cameras may generate electronic documents with full permissions to all users. This makes it difficult for users to identify appropriate filing locations and document permissions for these documents. In some cases, file storage may be provided to a user and shared between multiple advisor users associated with the user. This may cause challenges where information is not shared, or conversely, incorrectly shared with different advisor users. There exists a need for improved methods, systems, and computer readable media for providing automated document permissions associated with shared document storage. SUMMARY In a first aspect, some embodiments of the invention provide a method for determining the permissions of an electronic file, the method comprising: providing, at a memory in communication with a processor, a permissions database, the permissions database comprising a plurality of users, a plurality of advisors, and a plurality of categories; receiving, at a network device in communication with the processor, a candidate document; identifying from the candidate document, at the processor, a candidate user in the plurality of users, a candidate document routing action, and a candidate document category in the plurality of document categories; generating, at the processor, a candidate document permission attribute based on the candidate document in the permissions database, the candidate document permission attribute identifying the candidate user, a candidate file location based on the candidate document routing action, and the candidate document category; storing, in a storage system, the candidate document; and storing, in the memory, the candidate document permission attribute corresponding to the candidate document in the permissions database. In one or more embodiments, the method may further comprise assigning a category permission to an advisor in the plurality of advisors, the category permission corresponding to a first document category in the plurality of categories. In one or more embodiments, the method may further comprise: when the candidate document category matches the category permission of the candidate advisor, displaying, at a device of the candidate advisor, the candidate document. In one or more embodiments, the candidate document category may be determined based on a classification from a machine learning model. In one or more embodiments, the candidate document category may be determined based on a rule-based category model. In one or more embodiments, the candidate document routing action may comprise a candidate organization of the candidate document. In one or more embodiments, the candidate document category may further comprise a category identifier and a sub-category identifier. In one or more embodiments, the category identifier and the sub-category-identifier may define the candidate file location within a file hierarchy. In one or more embodiments, the candidate document may have a metadata item associated therewith, and the generating the candidate document category may be based