Hierarchy-based secured document repository
Techniques are provided for implementing and using a hierarchy-based secured document repository. The invention, the repository allows each user access to documents based on the position(s) held by the user in the hierarchy of a company. In one embodiment, the repository includes data that reflects the hierarchy of a company (“hierarchy data”), where the hierarchy includes nodes and relationships between nodes. The repository also includes user-to-node mapping data that maps users to one or more nodes, and document-to-node mapping data that maps documents to nodes. An access mechanism is provided that determines which document a user is able to access based on the hierarchy data, the user-to-node mapping data, and the document-to-node mapping data. In one embodiment, a user is allowed to access only those documents that are (1) mapped to the same node as the user, or (2) mapped to nodes that are below (relative to the hierarchy) any of the nodes to which the user is mapped.
1. A computer implemented method for providing users associated with an organization access to documents that belong to a set of documents, comprising the steps of:
storing hierarchy data that identifies
a set of nodes that correspond to ORG-UNITS associated with the organization; and
hierarchical relationships between said nodes that reflect hierarchical relationships between the ORG-UNITS that correspond to said nodes;
establishing a first mapping between the users and the set of nodes based on the ORG-UNITS to which the users belong;
establishing a second mapping between the documents in said set of documents and the set of nodes; and
determining which documents in said set of documents a user is allowed to access based on the hierarchy data, the first mapping and the second mapping.
2. The method of claim 1 wherein the step of determining includes determining that the user may access only a subset of documents in said set of documents, wherein said subset includes only documents that either:
map to a node to which the user maps; or
map to a node that, according to said hierarchical relationships, resides below a node to which the user maps.
3. The method of claim 2 further comprising the step of allowing the user to access the subset of documents without conveying to said user any information about documents in said set of documents that are not in said subset.
4. The method of claim 1 further comprising the step of automatically synchronizing the hierarchy data based on a new set of hierarchy information.
5. The method of claim 4 wherein the step of automatically synchronizing includes the steps of:
inserting nodes that appear in the new set of hierarchy information but not in the hierarchy data into the hierarchy data;
moving nodes that have new positions in the new set of hierarchy information to new positions in the hierarchy data; and
deleting nodes that appear in the hierarchy data but not in the new set of hierarchy information.
6. The method of claim 5 wherein the step of inserting is performed before the step of moving, and the step of moving is performed before the step of deleting.
7. The method of claim 5 wherein the step of inserting involves traversing the hierarchy represented by the new hierarchy information.
8. The method of claim 7 wherein the step of traversing is performed using a transversal technique that ensures parent nodes are processed before their children nodes.
9. The method of claim 8 wherein the step of traversing is performed using a left-most tree transversal.
10. The method of claim 1 wherein the step of determining which documents said user is allowed to access is performed in response to a request received by a web server over a network from a browser on a client being used by said user.
11. The method of claim 1 further comprising the steps of:
storing said set of documents in a repository accessible to said server; and
providing from said repository to said user over said network one or more documents that said user is allowed to access.
12. The method of claim 11 further comprising the step of implementing said repository in a relational database system.
13. A computer-readable storage medium carrying instructions for providing users associated with an organization access to documents that belong to a set of documents, the instructions including instructions for performing the steps of:
storing hierarchy data that identifies
a set of nodes that correspond to ORG-UNITS associated with the organization; and
hierarchical relationships between said nodes that reflect hierarchical relationships between the ORG-UNITS that correspond to said nodes;
establishing a first mapping between the users and the set of nodes based on the ORG-UNITS to which the users belong;
establishing a second mapping between the documents in said set of documents and the set of nodes; and
determining which documents in said set of documents a user is allowed to access based on the hierarchy data, the first mapping and the second mapping.
14. The computer-readable medium of claim 13 wherein the step of determining includes determining that the user may access only a subset of documents in said set of documents, wherein said subset includes only documents that either:
map to a node to which the user maps; or
map to a node that, according to said hierarchical relationships, resides below a node to which the user maps.
15. The computer-readable medium of claim 14 further comprising instructions for performing the step of allowing the user to access the subset of documents without conveying to said user any information about documents in said set of documents that are not in said subset.
16. The computer-readable medium of claim 13 further comprising instructions for performing the step of automatically synchronizing the hierarchy data based on a new set of hierarchy information.
17. The computer-readable medium of claim 16 wherein the step of automatically synchronizing includes the steps of:
inserting nodes that appear in the new set of hierarchy information but not in the hierarchy data into the hierarchy data;
moving nodes that have new positions in the new set of hierarchy information to new positions in the hierarchy data; and
deleting nodes that appear in the hierarchy data but not in the new set of hierarchy information.
18. The computer-readable medium of claim 17 wherein the step of inserting is performed before the step of moving, and the step of moving is performed before the step of deleting.
19. The computer-readable medium of claim 17 wherein the step of inserting involves traversing the hierarchy represented by the new hierarchy information.
20. The computer-readable medium of claim 19 wherein the step of traversing is performed using a transversal technique that ensures parent nodes are processed before their children nodes.
21. The computer-readable medium of claim 20 wherein the step of traversing is performed using a left-most tree transversal.
22. The computer-readable medium of claim 13 wherein the step of determining which documents said user is allowed to access is performed in response to a request received by a web server over a network from a browser on a client being used by said user.
23. The computer-readable medium of claim 13 further comprising instructions for performing the steps of:
storing said set of documents in a repository accessible to said server; and
providing from said repository to said user over said network one or more documents that said user is allowed to access.
24. The computer-readable medium of claim 23 further comprising instructions for performing the step of implementing said repository in a relational database system.