Access permissions management system and method
First Claim
Patent Images
1. In a hierarchical access permissions environment, a method for enabling efficient management of project-wise permissions, the method comprising using at least one processor and at least one memory comprising computer code for:
- maintaining project-wise lists of unstructured network objects, access permissions to which cannot be managed together via either a hierarchical folder structure or a single unstructured network object, whereineach of the unstructured network objects being distinctly different from one another and being represented by a link corresponding to at least one structured object stored on a disparate computing system;
the access permissions to the unstructured network objects not being extracted by an unstructured network object from another unstructured network object;
employing the project-wise lists of the unstructured network objects to make project-wise changes in the access permissions to the unstructured network objects without the need to individually modify access permissions to individual ones of the unstructured network objects; and
in response to the changes being made in the unstructured network objects, propagating the changes to at least one structured object stored on the disparate computing system.
0 Assignments
0 Petitions
Accused Products
Abstract
In a hierarchical access permissions environment, a method for enabling efficient management of project-wise permissions including maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure and employing the project-wise lists of network objects to make project-wise changes in access permissions to the network objects without the need to individually modify access permissions to individual ones of the network objects.
-
Citations
16 Claims
-
1. In a hierarchical access permissions environment, a method for enabling efficient management of project-wise permissions, the method comprising using at least one processor and at least one memory comprising computer code for:
-
maintaining project-wise lists of unstructured network objects, access permissions to which cannot be managed together via either a hierarchical folder structure or a single unstructured network object, wherein each of the unstructured network objects being distinctly different from one another and being represented by a link corresponding to at least one structured object stored on a disparate computing system; the access permissions to the unstructured network objects not being extracted by an unstructured network object from another unstructured network object; employing the project-wise lists of the unstructured network objects to make project-wise changes in the access permissions to the unstructured network objects without the need to individually modify access permissions to individual ones of the unstructured network objects; and in response to the changes being made in the unstructured network objects, propagating the changes to at least one structured object stored on the disparate computing system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. In a hierarchical access permissions environment, a project management system including a non-transitory, tangible computer-readable medium in which computer program instructions are stored, which instructions, when read by a computer, cause the computer to enable efficient management of project-wise permissions, the system comprising:
-
a project-wise lists management (PWLM) subsystem maintaining project-wise lists of unstructured network objects, access permissions to which cannot be managed together via either a hierarchical folder structure or a single unstructured network object, wherein each of the unstructured network objects being distinctly different from one another and being represented by a link corresponding to at least one structured object stored on a disparate computing system; the access permissions to the unstructured network objects not being extracted by an unstructured network object from another unstructured network object; and a user interface allowing an owner of a project-wise list of the unstructured network objects to make project-wise changes in the access permissions to the unstructured network objects without the need to individually modify access permissions to individual ones of the unstructured network objects; and in response to the changes being made in the unstructured network objects, propagating the changes to at least one structured object stored on the disparate computing system. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
Specification