Access permissions management system and method

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.

Description

REFERENCE TO RELATED APPLICATIONS

Reference is made to U.S. patent application Ser. No. 13/014,762, filed Jan. 27, 2011, and entitled “AUTOMATIC RESOURCE OWNERSHIP ASSIGNMENT SYSTEMS AND METHODS”, the disclosure of which is hereby incorporated by reference and priority of which is hereby claimed pursuant to 37 CFR 1.78(a) (1) and (2)(i).

Reference is also made to U.S. Provisional Patent Application Ser. No. 61/477,662, filed Apr. 21, 2011 and entitled “ACCESS PERMISSIONS MANAGEMENT SYSTEM AND METHOD”, the disclosure of which is hereby incorporated by reference and priority of which is hereby claimed pursuant to 37 CFR 1.78(a) (4) and (5)(i).

Reference is also made to U.S. patent application Ser. No. 13/106,023, filed May 12, 2011, and entitled “AUTOMATIC RESOURCE OWNERSHIP ASSIGNMENT SYSTEM AND METHOD”, the disclosure of which is hereby incorporated by reference and priority of which is hereby claimed pursuant to 37 CFR 1.78(a) (1) and (2)(i).

Reference is also made to U.S. patent application Ser. No. 13/159,903, filed Jun. 14, 2011, and entitled “ACCESS PERMISSIONS MANAGEMENT SYSTEM AND METHOD”, the disclosure of which is hereby incorporated by reference and priority of which is hereby claimed pursuant to 37 CFR 1.78(a) (1) and (2)(i).

Reference is also made to the following patents and patent applications, owned by assignee, the disclosures of which are hereby incorporated by reference:

U.S. Pat. Nos. 7,555,482 and 7,606,801;

U.S. Published Patent Application Nos. 2007/0244899, 2008/0271157, 2009/0100058, 2009/0119298; 2009/0265780; 2011/0010758; 2011/0060916; 2011/0061093; 2011/0061111 and 2011/0184989;

U.S. patent application Ser. Nos. 12/861,059; 12/861,953; 13/106,023 and 13/159,903; and

PCT Applications PCT/IL2011/000409 and PCT/IL2011/000408.

FIELD OF THE INVENTION

The present invention relates to data management generally and more particularly access permissions management.

BACKGROUND OF THE INVENTION

The following patent publications are believed to represent the current state of the art:

U.S. Pat. Nos. 5,465,387; 5,899,991; 6,338,082; 6,393,468; 6,928,439; 7,031,984; 7,068,592; 7,403,925; 7,421,740; 7,555,482, 7,606,801 and 7,743,420; and

U.S. Published Patent Application Nos.: 2003/0051026; 2004/0249847; 2005/0108206; 2005/0203881; 2005/0086529; 2006/0064313; 2006/0184530; 2006/0184459; 2007/0203872; 2007/0244899; 2008/0271157; 2009/0100058; 2009/0119298 and 2009/0265780.

SUMMARY OF THE INVENTION

The present invention provides improved systems and methodologies for access permissions management.

There is thus provided in accordance with a preferred embodiment of the present invention 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.

In accordance with a preferred embodiment of the present invention maintaining project-wise lists of network objects includes generating at least one project-wise list of plural ones of the network objects. Preferably, maintaining project-wise lists of network objects also includes mapping access permissions of the plural ones of the network objects onto the at least one project-wise list. Preferably, maintaining project-wise lists of network objects also includes merging access permissions of plural ones of first network objects of a first project-wise list with access permissions of corresponding plural ones of second network objects of a second project-wise list.

In accordance with a preferred embodiment of the present invention the network objects are stored on disparate computers. In accordance with a preferred embodiment of the present invention at least some of the disparate computers are operated by different computer operating systems. In accordance with a preferred embodiment of the present invention the network objects include inter-related subject matter.

Preferably, the network objects are owned by a common owner.

There is also provided in accordance with another preferred embodiment of the present invention in a hierarchical access permissions environment, a project management system for enabling efficient management of project-wise permissions including a project-wise lists management (PWLM) subsystem maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure and a user interface allowing an owner of a project-wise list 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.

In accordance with a preferred embodiment of the present invention the project-wise lists management (PWLM) subsystem includes a project-wise list generator which generates at least one project-wise list of plural ones of the network objects. Preferably, the project-wise lists management (PWLM) subsystem also includes an access permissions mapping generator which maps access permissions of the plural ones of the network objects onto the at least one project-wise list. Preferably, the project-wise lists management (PWLM) subsystem also includes project-wise lists merging functionality which is operative to merge access permissions of plural ones of first network objects of a first project-wise list with access permissions of corresponding plural ones of second network objects of a second project-wise list.

In accordance with a preferred embodiment of the present invention the network objects are stored on disparate computers. In accordance with a preferred embodiment of the present invention at least some of the disparate computers are operated by different computer operating systems. In accordance with a preferred embodiment of the present invention the network objects include inter-related subject matter.

Preferably, the network objects are owned by a common owner.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:

FIG. 1 is a simplified pictorial illustration of one example of the use of a system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention;

FIG. 2 is a simplified flowchart indicating steps in the operation of the system of FIG. 1;

FIG. 3 is a simplified pictorial illustration of another example of the use of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention;

FIG. 4 is a simplified flowchart indicating steps in the operation of the system of FIG. 3;

FIGS. 5A and 5B are simplified pictorial illustrations of yet another example of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention;

FIGS. 6A and 6B are simplified pictorial illustrations of still another example of the use of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention;

FIG. 7 is a simplified flowchart indicating steps in the operation of the system of FIGS. 6A and 6B;

FIGS. 8A and 8B are simplified pictorial illustrations of still another example of the use of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention; and

FIG. 9 is a simplified flowchart indicating steps in the operation of the system of FIGS. 8A and 8B.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference is now made to FIG. 1, which is a simplified pictorial illustration of the use of a project management system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention. This system is preferably suitable for operating in an hierarchical access permissions environment such as an enterprise computer network including multiple network objects, and includes a project-wise lists management (PWLM) subsystem maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure, and a user interface allowing an owner of a project-wise list 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.

The term “network object” for the purposes of this application is defined to include user generated enterprise computer network resources on any commercially available computer operating system. Examples of network objects include structured and unstructured computer data resources such as files and folders, mailboxes and mailing lists, disparate users, user groups and collections of user groups, and physical resources controlled by an enterprise computer network such as doors, parking lots and elevators.

As shown in FIG. 1, on a particular date such as Jan. 15, 2011, a CEO of a first company informs the IT manager of the company of an imminent merge with a second company, and requests that the IT manager merge the user groups of the two companies within two weeks. In response, the IT manager informs the CEO that he is unable to execute the merge.

As also shown in FIG. 1, the CEO of the second company informs the IT manager of the second company of the imminent merge with the first company, and requests that the IT manager merge the user groups of the two companies within two weeks. As seen in FIG. 1, the IT manager of the second company has access to a project management system 100. It is appreciated that project management system 100 is operative to make project-wise changes in access permissions to network objects without the need to individually access individual ones of the network objects.

Reference is now made to FIG. 2, which is a simplified flowchart indicating steps in the operation of the system of FIG. 1. The example of FIG. 2 illustrates the use of the project management system in merging corresponding user groups of two existing distinct lists of user groups into one new list of user groups, thereby enabling the users belonging to the groups of the two existing lists to be managed together.

As shown in FIG. 2, to initiate the merge (200), a user selects a first list of groups (202) and a second list of groups (204) to be merged. To each group in the first list, the system preferably adds the members of a corresponding group in the second list (206). Similarly, to each group in the second list, the system preferably adds the members of a corresponding group in the first collection (208).

The system then creates a third list of groups (210) and copies all groups of the first and second lists to the third list (212). Similarly, the system copies the authorizers of the first and second lists (214) and the rules of the first and second lists (216) to the third list. For the purposes of this application, “authorizers” are defined as users who have been granted limited management rights to a list, and “rules” are defined as a set of conditions under which users may be added or removed from a list.

Thereafter, the system assigns ownership of the third list to the owners of the first and second lists (218), and deletes the first and second lists (220).

Reference is now made to FIG. 3, which is a simplified pictorial illustration of another example of the use of the project management system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention. This system is preferably suitable for operating in an hierarchical access permissions environment including multiple network objects, and includes functionality for maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure, and functionality for 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 access individual ones of the network objects.

As shown in FIG. 3, there is provided a project management system which typically resides on a server 300 that is connected to an enterprise-wide network 302. Network 302 preferably includes multiple disparate clients 304 and file servers 306. Each of file servers 306 preferably hosts a hierarchical folder structure 308 of folders and files.

The project management system residing on server 300 preferably comprises a projects repository 320 which contains a plurality of project-wise lists of links to network objects. In the example of FIG. 3, projects repository 320 includes a list of links to HR related folders 322, a list of links to legal related folders 324 and a list of links to finance related folders 326. Each of project-wise lists 322, 324 and 326 preferably comprises links 330 which reference actual folders 332 residing in any of hierarchical folder structures 308 hosted on file servers 306.

It is a particular feature of this embodiment of the present invention that although actual folders 332 referenced by links 330 in each of project-wise lists 322, 324 and 326 may each reside in any of hierarchical folder structures 308 hosted on disparate file servers 306, each of project-wise lists 322, 324 and 326 may be employed to make changes in access permissions to the folders referenced by links 330 thereof without the need to individually access individual ones of actual folders 332.

In the example of FIG. 3, an HR manager of a company introduces John, a new employee of the HR department, to the IT manager of the company, and requests that the IT manager grant John access permissions to all HR files in the organization. In response to the request made by the HR manager, the IT manager utilizes the project management system residing on server 300 to grant John permissions to the project-wise list of HR related folders 322, thereby granting John permissions to the portion of actual folders 332 which are HR related.

Reference is now made to FIG. 4, which is a simplified flowchart indicating steps in the operation of the system of FIG. 3. The example of FIG. 4 illustrates the use of the project management system in modifying access permissions to folders residing on disparate file servers without the need to individually access individual ones of the folders.

As shown in FIG. 4, initially, a new project-wise list is created (400). Preferably, an owner of the new project-wise list then adds links to actual folders which preferably reside on disparate file servers to the new project-wise list (402). The owner can then grant access permissions to the new project-wise list to individuals (404). The access permissions granted to the new project-wise list are then propagated by the system to actual folders via the links (406), thereby granting actual access permissions to the actual folders to the individuals.

Reference is now made to FIGS. 5A and 5B, which are simplified pictorial illustrations of yet another example of the use of the project management system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention. This system is preferably suitable for operating in an hierarchical access permissions environment including multiple network objects, and includes functionality for maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure, and functionality for 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 access individual ones of the network objects.

As shown in FIG. 5A on a particular date such as Jan. 15, 2011, an HR manager of a company requests an IT manager of the company to enable her to centrally manage HR related files and folders which reside on file servers hosted on diverse computer platforms located in disparate geographic locations. The IT manager informs the HR manager that the disparately located files and folders cannot be jointly managed as they reside on file servers hosted on diverse computer platforms. Responsive to the response of the IT manager, the HR manager terminates the employment of the IT manager at the company.

Turning now to FIG. 5B, it is shown that on a later date, such as on Jan. 20, 2011, the HR manager requests a newly hired IT manager of the company to enable her to centrally manage HR related files and folders which reside on file servers hosted on diverse computer platforms located in disparate geographic locations. The IT manager informs the HR manager that this can readily be achieved.

As shown in FIG. 5B, the IT manager has access to a project management system which typically resides on a server 500 that is connected to an enterprise-wide network 502. Network 502 preferably includes multiple disparate clients 504 and multiple disparate file servers 506 located in disparate geographic locations. Each of file servers 506 preferably hosts a hierarchical folder structure 508 of folders and files.

The project management system residing on server 500 preferably comprises a projects repository 520 which contains a plurality of project-wise lists of links to network objects. In the example of FIG. 5B, projects repository 520 includes a list of links to legal related folders 524 and a list of links to finance related folders 526. Each of lists 524 and 526 preferably comprises links 530 which reference actual folders residing in any of hierarchical folder structures 508 hosted on file servers 506.

As further shown in FIG. 5B, the IT manager employs the project management system residing on server 500 to create a new list of links to actual HR related folders 538 which folders reside on servers 506 located in disparate geographic locations. The IT manager selects an HR related folder in the United Kingdom 540, an HR related folder in the United States 542, and an HR related folder in France 544 and adds them to new list 538, thereby creating new corresponding links 550, 552 and 554. After completing the creation of new list 538, list 538 may be employed to centrally manage disparately located HR related folders 540, 542 and 544.

It is a particular feature of this embodiment of the present invention that although actual folders 540, 542 and 544 referenced by new list 538 may each reside in any of hierarchical folder structures 508 hosted on diverse computer platforms of disparate file servers 506, new list 538 may be employed to make changes in access permissions to the folders referenced thereby without the need to individually access individual ones of actual folders 540, 542 and 544.

Reference is now made to FIGS. 6A and 6B, which are simplified pictorial illustrations of still another example of the use of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention. This system is preferably suitable for operating in an hierarchical access permissions environment including multiple network objects, and includes functionality for maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure, and functionality for 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 access individual ones of the network objects.

As shown in FIG. 6A, there is provided a project management system which typically resides on a server 600 that is connected to an enterprise-wide network 602. Network 602 preferably includes multiple disparate clients 604, file servers 606 and email servers 607. Each of file servers 606 preferably hosts a hierarchical folder structure 608 of folders and files. Each of email servers 607 preferably hosts a plurality of mailboxes and mailing lists 610.

The project management system residing on server 600 preferably comprises a projects repository 620 which contains a plurality of project-wise lists of links to network objects. In the example of FIG. 6A, projects repository 620 includes a list of HR related links 622, a list of legal related links 624 and a list of finance related links 626. Each of lists 622, 624 and 626 preferably comprises links 630 which reference actual folders 632 residing in any of hierarchical folder structures 608 hosted on file servers 606. Additionally, each of lists 622, 624 and 626 preferably comprises links 634 which reference actual mailboxes and mailing lists 610 residing in any of email servers 607.

It is a particular feature of this embodiment of the present invention that although actual folders 632 and mailboxes and mailing lists 610 referenced in each of lists 622, 624 and 626 may each reside in any of hierarchical folder structures 608 hosted on disparate file servers 606 and on disparate email servers 607 respectively, each of lists 622, 624 and 626 may be employed to make changes in access permissions to actual folders 632 and mailboxes and mailing lists 610 referenced by links thereof without the need to individually access individual ones of actual folders 632 and mailboxes and mailing lists 610.

In the example of FIG. 6A, on a particular date such as Jan. 5, 2011, an HR manager of a company introduces Frank, a new employee of the HR department, to the IT manager of the company, and requests that the IT manager grant Frank access permissions to all HR files and HR mailing lists in the organization. In response to the request made by the HR manager, the IT manager utilizes the project management system residing on server 600 to grant Frank permissions to the list of HR related links 622, thereby granting Frank permissions to the portion of actual folders 632 and mailboxes and mailing lists 610 which are HR related.

Turning now to FIG. 6B, it is shown that on a later date, such as on Jan. 6, 2011, Frank attempts to access an HR related email item 650. Upon entering suitable identification credentials, Frank is granted access to the HR related email item 650.

Reference is now made to FIG. 7, which is a simplified flowchart indicating steps in the operation of the system of FIGS. 6A and 6B. The example of FIG. 7 illustrates the use of the project management system in modifying access permissions to folders, mailboxes and mailing lists residing on disparate file servers and email servers without the need to individually access individual ones of the folders, mailboxes and mailing lists.

As shown in FIG. 7, initially, a new project-wise list is created (700). Preferably, an owner of the new project-wise list then adds links to actual folders which preferably reside on disparate file servers to the new project-wise list (702). Preferably, the owner of the new project-wise list also adds links to actual mailboxes and mailing lists which preferably reside on disparate email servers to the new project-wise list (704). The owner can then grant access permissions to the new project-wise list to individuals (706). The access permissions granted to the new project-wise list are then propagated by the system to actual folders, mailboxes and mailing lists via the links (708), thereby granting actual access permissions to the actual folders to the individuals.

Reference is now made to FIGS. 8A and 8B, which are simplified pictorial illustrations of still another example of the use of the system for enabling efficient management of project-wise permissions, constructed and operative in accordance with a preferred embodiment of the present invention. This system is preferably suitable for operating in an hierarchical access permissions environment including multiple network objects, and includes functionality for maintaining project-wise lists of network objects, access permissions to which cannot be managed together via a hierarchical folder structure, and functionality for 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 access individual ones of the network objects.

As shown in FIG. 8A, there is provided a project management system which typically resides on a server 800 that is connected to an enterprise-wide network 802. Network 802 preferably includes multiple disparate clients 804, file servers 806 and a facility security server 807. Each of file servers 806 preferably hosts a hierarchical folder structure 808 of folders and files. Facility security server 807 preferably controls physical access to various areas of a facility by controlling the opening and closing of doorways throughout the facility via a plurality of doorway access permissions records 810.

The project management system residing on server 800 preferably comprises a projects repository 820 which contains a plurality of project-wise lists of links to network objects. In the example of FIG. 8A, projects repository 820 includes a list of HR related links 822, a list of legal related links 824 and a list of finance related links 826. Each of lists 822, 824 and 826 preferably comprises links 830 which reference actual folders 832 residing in any of hierarchical folder structures 808 hosted on file servers 806. Additionally, each of lists 822, 824 and 826 preferably comprises links 834 which reference doorway access permissions records 810 residing on facility security server 807.

It is a particular feature of this embodiment of the present invention that although actual folders 832 and doorway access permissions records 810 referenced in each of lists 822, 824 and 826 may each reside in any of hierarchical folder structures 808 hosted on disparate file servers 806 and on facility security server 807 respectively, each of lists 822, 824 and 826 may be employed to make changes in access permissions to actual folders 832 and in doorway access permissions records 810 referenced by links thereof without the need to individually access individual ones of actual folders 832 and doorway access permissions records 810.

In the example of FIG. 8A, on a particular date such as Jan. 5, 2011, an HR manager of a company introduces Jim, a new employee of the finance department, to the IT manager of the company, and requests that the IT manager grant Jim access permissions to all finance files and access to the finance offices located within the company's facility. In response to the request made by the HR manager, the IT manager utilizes the project management system residing on server 800 to grant Jim permissions to the finance list 822, thereby granting Frank permissions to the portion of actual folders 832 which are finance related and access to the finance offices located within the company's facility.

Turning now to FIG. 8B, it is shown that on a later date, such as on Jan. 6, 2011, Jim attempts to open a doorway 850 to an area in the facility which is restricted to individuals with access permissions to the finance department. Upon entering suitable identification credentials such as an access card 852, Jim is granted access to doorway 850.

Reference is now made to FIG. 9, which is a simplified flowchart indicating steps in the operation of the system of FIGS. 8A and 8B. The example of FIG. 9 illustrates the use of the project management system in modifying access permissions to folders and to various physical areas of a facility.

As shown in FIG. 9, initially, a new project-wise list is created (900). Preferably, an owner of the new project-wise list then adds links to actual folders which preferably reside on disparate file servers to the new project-wise list (902). Preferably, the owner of the new project-wise list also adds links to actual doorway access permissions records which preferably reside on a facility security server to the new project-wise list (904). The owner can then grant access permissions to the new project-wise list to individuals (906). The access permissions granted to the new project-wise list are then propagated by the system to actual folders and doorway access permissions records via the links (908), thereby granting actual access permissions to the actual folders to the individuals.

It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove as well as modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not in the prior art.

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; andin 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.

2. The method according to claim 1, wherein the maintaining project-wise lists of the unstructured network objects comprises generating at least one project-wise list of plural ones of the unstructured network objects.

3. The method according to claim 2, wherein the maintaining project-wise lists of the unstructured network objects also comprises mapping access permissions of the plural ones of the unstructured network objects onto the at least one project-wise list.

4. The method according to claim 1, wherein the maintaining project-wise lists of the unstructured network objects also comprises merging access permissions of plural ones of first unstructured network objects of a first project-wise list with access permissions of corresponding plural ones of second unstructured network objects of a second project-wise list.

5. The according to claim 1, wherein the unstructured network objects are stored on disparate computers.

6. The method according to claim 5, wherein at least some of the disparate computers are operated by different computer operating systems.

7. The method according to claim 1, wherein the unstructured network objects comprise inter-related subject matter.

8. The method according to claim 1 and wherein the unstructured network objects are owned by a common owner.

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, 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; anda 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; andin 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.

10. The project management system according to claim 9, wherein the project-wise lists management (PWLM) subsystems comprises: a project-wise list generator which generates at least one project-wise list of plural ones of the unstructured network objects.

11. The project management system according to claim 10, wherein the project-wise lists management (PWLM) subsystem also comprises: an access permissions mapping generator which maps access permissions of the plural ones of the unstructured network objects onto the at least one project-wise list.

12. The project management system according to claim 9, wherein the project-wise lists management (PWLM) subsystem also comprises: project-wise lists merging functionality which is operative to merge access permissions of plural ones of first unstructured network objects of a first project-wise list with access permissions of corresponding plural ones of second unstructured network objects of a second project-wise list.

13. The project management system according to claim 9, wherein the unstructured network objects are stored on disparate computers.

14. The project management system according to claim 13, wherein at least some of the disparate computers are operated by different computer operating systems.

15. The project management system according to claim 9, wherein the unstructured network objects comprise inter-related subject matter.

16. The project management system according to claim 9 and wherein the unstructured network objects are owned by a common owner.