WO2000051033A2

WO2000051033A2 - Dynamic sites

Info

Publication number: WO2000051033A2
Application number: PCT/US2000/004743
Authority: WO
Inventors: Jaymz Dilworth; Alan Mcmillan; Danimir Ljepava; Aleksander Susnjar
Original assignee: Planet-Intra.Com
Priority date: 1999-02-23
Filing date: 2000-02-23
Publication date: 2000-08-31
Also published as: WO2000051033A3; WO2000051033A9

Abstract

An automatic system is provided in which users from their browsers and while on-line, can manipulate site directories and documents by, for example, adding, deleting, moving, and copying. The system engine uses a storage to store information on particular use of a directory and document structure on a server. A user makes a request through the Web browser that is processed using technologies, including, for example, an executable CGI module. In this way, the directory and document structure of a site can be changed. The system is simple to use and does not require extensive computer knowledge, and there is no need for an administrator to manually perform described functions.

Description

Dynamic Sites

BACKGROUND OF THE INVENTION

TECHNICAL FIELD

The present invention relates to computer directory structures. More particularly, the present invention relates to dynamic directory structures related to World Wide Web (Web) sites.

DESCRIPTION OF THE PRIOR ART

An intranet is like a mini Internet and is used in various industries. A World Wide Web (Web) browser is used to display intranet information to an end- user on Web pages and it also provides a way for the end-user to navigate through the intranet information. However, unlike the Internet, only individuals who have been granted access to the intranet will see the information.

The present solution to making the information of the intranet available for viewing requires a site administrator or an end-user with extensive computer knowledge to upload manually the information to the intranet. In addition, typically only site administrators are empowered to change a directory structure on the intranet, and to perform directory and file structure manipulations such as, for example, copy, move, add, delete, and rename. These processes must be done manually and are laborious and time consuming.

R. E. Wesinger, Jr. et al, Web Server Employing Multi-homed, Modular Framework, U.S. Patent No. 5,870,550 (Feb. 9, 1999) discloses a Web server having a multi-homed, modular framework. The modular framework allows extensions to the Web server to be easily compiled into the Web server, allowing the extensions to run natively as part of the server instead of incurring the overhead typical of CGI scripts, for example. The multi-homing capabilities of the Web server provide the appearance to Web users of multiple distinct and independent servers, allowing a small company or individual to create the same kind of Web presence enjoyed by larger companies. In effect, multiple virtual servers run on the same physical machine. The Web server as a whole is easily extensible to allow additional capabilities to be provided natively within the Web server itself. Furthermore, each virtual server is independently configurable in order to turn different capabilities on or off or to modify operation of the virtual server. The Web server is also provided with enhanced security features, built-in animation capability, and other features that afford maximum flexibility and versatility.

The Wesinger, Jr. et al teachings provide the appearance to Web users of multiple distinct and independent servers, but does not teach nor suggest providing means for a typical user to manipulate a server directory structure at all or dynamically.

E. Leshem et al, Software System and Associated Methods for Facilitating the Analysis and Management of Web Sites, U.S. Patent No. 5,870,559 (Feb. 9, 1999) discloses a visual Web site analysis program, implemented as a collection of software components, which provides a variety of features for facilitating the analysis and management of Web sites and Web site content. A mapping component scans a Web site over a network connection and builds a site map which graphically depicts the URLs and links of the site. Site maps are generated using a unique layout and display methodology which allows the user to visualize the overall architecture of the Web site. Various map navigation and URL filtering features are provided to facilitate the task of identifying and repairing common Web site problems, such as links to missing URLs. A dynamic page scan feature enables the user to include dynamically-generated Web pages within the site map by capturing the output of a standard Web browser when a form is submitted by the user, and then automatically resubmitting this output during subsequent mappings of the site. The Web site analysis program is implemented using an extensible architecture which includes an API that allows plug-in applications to manipulate the display of the site map. Various plug-ins are provided which utilize the API to extend the functionality of the analysis program, including an action tracking plug-in which detects user activity and behavioral data (link activity levels, common site entry and exit points, etc.) from server log files and then superimposes such data onto the site map.

The E. Leshem et al disclosure does not teach or suggest enabling an ordinary user to manipulate the site's directory structure at all or dynamically.

R. E. Wesinger, Jr. et al, Automated On-line Information Service and Directory, Particularly for the World Wide Web, U.S. Patent No. 5,778,367 (Jul. 7, 1998) discloses a computer network and a database used to provide a hardware-independent, dynamic information system in which the information content is entirely user-controlled. Requests are received from individual users of the computer network to electronically publish information, and input is accepted from the individual users. Entries from the users containing the information to be electronically published are automatically collected, classified and stored in the database in searchable and retrievable form. Entries are made freely accessible on the computer network. In response to user requests, the database is searched and entries are retrieved. Entries are served to users in a hardware-independent page description language. The entries are password protected, allowing users to retrieve and update entries by supplying a correct password. Preferably, the process is entirely automated with any necessary billing being performed by secure, on-line credit card processing. The user making a database entry has complete control of that entry both at the time the entry is made and in the future after the entry has been made. The entry, when served to a client, is transformed on-the-fly to the page description language. Where the page description language is HTML and the computer network is the World Wide Web, the entry may function as a "mini" homepage for the user that made the entry. Provision is made for graphics and other kinds of content besides text, taking advantage of the content-rich nature of the Web. The Wesinger, Jr. et al disclosure does not teach or suggest enabling a common user or plurality of users to access a same space on a server and to manipulate its structure. The disclosure focuses on a user contributing a single document, analogous to a mini home page, as opposed to manipulating the organization structure of a plurality of directories and documents.

J. Logan et al, Interactive System for Authoring Hypertext Document Collections, U.S. Patent No. 5,802,299 (Sep. 1 , 1998) discloses a network based hypertext display system employing a supervisory computer interconnected with one or more information display units and one or more remote document servers via a network, such as the Internet. The supervisory computer controls the content displayed by the display units by transferring to each unit a control information file as well as hypertext document files which are locally stored in the display units. The control file determines the extent to which the display unit can access remotely stored information and provides additional information which is used to alter the presentation to the user. Stored control information is used to rewrite hypertext document such that certain links are disabled, and to suppress the appearance of visual cues associated with the displayed anchor which identifies selected links in the referencing document. Links and other information in local and remotely accessed documents are rewritten in accordance with commands created by a content developer using an interactive content authoring system. Means are employed for controlling the duration of a given user session in response to the material selected for display, the time of day, and user demographics. Locally stored data copied from original documents stored on remote servers is periodically validated and updated when the validation indicates that the original has been modified.

J. Logan ef al disclosure does not teach or suggest the user is the common end-user. It does not teach or suggest directory structures or file structures being manipulated dynamically by the common end-user and while on-line. it would be advantageous to provide a simpler environment with tools that lets anyone within an organization contribute information on-line, for example to the corporate intranet, and to provide a highly organized structure to organize such information, wherein the individual does not have to have extensive HTML language knowledge, knowledge of Internet protocols, or extensive computer knowledge, and thereby greatly expand such opportunities to possibly 98% of the intranet users.

It would be advantageous to provide a dynamic directory structure which enables users of an Intranet/Internet site to manage its content dynamically, such as, for example, the addition, removal, copying, and moving of directories and documents of a site.

It would be advantageous to provide a dynamic directory structure which eliminates the step of the uploading of directory structure of documents.

SUMMARY OF THE INVENTION

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 is a block diagram showing the hierarchical relationship of the three example levels according to the invention; and Fig. 2 is a block diagram showing the relationship of the main components according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

Share Information with others within a company

According to a preferred embodiment of the invention, anybody in a company that uses the invention can share information on-line, on the company's intranet, for example, provided a system administrator grants the individual permission to post documents. Any authorized user can access the system administration. Within system administration are objects, such as, for example, titles of departments, their subcategories, page titles, and links to which the authorized user can, for example, add, change, move or delete information. It is noted that a user works live on a page.

It is noted that the term on-line means on a network system, and is not limited to a specific implementation of a network system. In a preferred embodiment, the meaning of on-line is on an intranet.

A preferred embodiment provides a structure wherein the generic concept of a folder is referred to as a department, and the generic concept of a subfolder is referred to as a group. This feature is provided to enable common end-users to relate more easily to the mechanics of the invention.

The invention herein provides simplicity to the end-user. A person with technical expertise and knowledge is not required. Everything is centralized and is done on-line, which saves steps required in the prior art. Ordinary end- users are empowered to perform directory and document navigation.

The invention herein provides an environment that lets anyone within an organization contribute information to the corporate intranet. It overcomes the two main obstacles usually inherited within a typical Intranet. First, it provides everyone the tools to contribute information, and second, it provides a highly organized structure to organize such information.

Managing the Content In a preferred embodiment, information is organized in levels of objects, wherein an object may itself be a level. The embodiment is organized in, but is not limited to being organized in a multi-level hierarchy model, wherein the depth of the structure, i.e. the number of nested levels, is not limited. The embodiment allows administrators to perform administrative functions as necessary. Each level can have administrators. The model allows administrators at one level to perform administrative functions within its level and within nested levels. Administrative functions include, for example, adding, removing, locking, and unlocking user accounts and setting up access privileges.

Example

In the following example herein below, information is organized, but is not limited to being organized in a three-level hierarchy model. The first level includes departments, the second level includes groups, and the third level includes documents. The example allows administrators to add and remove departments, groups and documents as necessary. Each department or group can have administrators. The administrators can also add, remove, lock, and unlock user accounts and set up access privileges. Contributing the Information

In a preferred embodiment, each level has areas. An area is for containing objects of the same type. In another embodiment, lists are provided to a user through the Web browser for viewing the contents of the areas.

Example

As an example of an implementation of areas, a group cited herein above has two areas. The first area is a document area containing documents prepared in a Java WYSIWYG editor. The second area is a file area containing uploaded files available for download. By viewing group content a user can select either a file or document list, or a list containing both files and documents.

It is noted that a preferred embodiment handles the submission of and structure of objects within levels. The embodiment stores content-type information about each object and displays such content as appropriate. In one embodiment, security system and user and administrative privileges are the same for all objects.

Example

The example herein of an implementation of the invention handles the submission and structure of documents within an intranet. The example stores content-type information about each file in file areas and according to the information displays an appropriate icon depending on the file displayed. Security system and user and administrative privileges are the same for both documents and files.

Security Issues

In a preferred embodiment, the server does not allow any direct access to information stored. All information is accessible only through a valid system account and a security engine. A user directory holds security data in addition to holding user information. Security data is used to manage system logins, permissions on levels, and nested levels for each and every user of the system, ensuring users can perform manipulations only when authorized to do so.

Example

In the following example herein, a user directory holds security data used to manage system logins, permissions on departments, groups and documents for each and every user of the system, ensuring the users can, for example, edit, modify, and delete documents only when authorized to do so. The server does not give any direct access to the information stored. All information is accessible only through a valid system account and a security engine.

Workspace Look and Feel

In the preferred embodiment, the workspace is divided into functional areas.

Example

In the following example herein, the workspace comprises, but is not limited to, a navigation panel and a content panel.

In the example herein, the navigation panel comprises a list of departments. Selecting or clicking on a department unrolls a list of groups inside the individual department. In one implementation, department headlines are shown in the content panel. The group list of a previously opened department, if any, collapses. By clicking on a group, the content panel will show a list of the documents stored inside the selected group. The list is ordered by modification date and time and in descending order. In the case of a large number of documents inside the group, the list is divided into several pages. In one embodiment, a search mechanism is available to find documents inside the group.

Also in the example herein, the content panel shows the result of the previous actions cited herein above. In one implementation, the content shows, but is not limited to company headlines, department headlines, a list of documents or files depending on a user's choice stored inside a group, document content, search forms, search results, and customizing forms and options.

Administration

In the preferred embodiment, administration is divided into categories or levels. Each level has one or more administrator, wherein the administrator can perform typical administrative functions comprising, but not limited to:

• All actions as a regular member of a level, though not necessarily done in the same way;

• Grants nested level membership to a member of parent level ; • Revokes level membership from a current level member;

• Deletes or otherwise modifies an object stored in a level;

• Changes access privileges of a level; and

• Views user and object statistics in the scope of the level.

Example

In the following example herein, administration is divided into three categories or levels. It is noted in this context the words categories and levels are interchangeable. The three levels are group administration, department administration, and top level administration.

Group administration.

In the cited example, each group has one or more group administrators. The group administrator performs any of, but is not limited to, the following:

• All actions as a regular member of a group, though not necessarily done in the same way;

• Grants a group membership to a member of parent department;

• Revokes a group membership from a current group member;

• Deletes or modifies a document stored in a group;

• Deletes or renames a file stored in a group's file area; • Changes access privileges of a group; and

• Views user and document statistics in the scope of a group.

Department administration. In the cited example, each department has one or more department administrators. The department administrator performs any of, but is not limited to, the following:

• All actions as a regular member of the department, though not necessarily done in the same way; • All actions group administrators can perform inside the administered department, though not necessarily in the same way;

• Grants a department membership to any user;

• Revokes a department membership from a current department member; • Creates or deletes a group inside a department;

• Grants or revokes group administration privileges among department members;

• Creates and edits department headlines;

• Moves or copies documents or files from one group to the other; and • Views department statistics.

Top level or root administration.

In the cited example, the system is required to have one or more top level administrators. The top level administrator performs any of, but is not limited to, the following:

• All actions as a regular user of the system, though not necessarily done in the same way;

• All actions of department and group administrators, though not necessarily in the same way; • Creates or deletes a department;

• Grants or revokes top level administration privileges, wherein it cannot revoke its own administrative privileges;

• Grants or revokes department administration privileges;

• Creates and edits the company main headlines; • Moves or copies documents or files from one department or group to another;

• Views system statistics, comprising, but not limited to: number of users, list of users, number of documents in the system per each department and per each group, number of departments, and number of groups per department; and • Adds new users and removes, locks, and unlock existing users.

It is noted that in one embodiment, only one user account exists by default after installation. The user account is the administrator with a blank password.

Fig. 1 is a block diagram showing from the example cited herein directly above the hierarchical relationship of the top level administrator, the department administrator, and the group administrator, according to the invention.

Permissions

In a preferred embodiment, category member are assigned attributes or flags specifying permissions granted for a given level. Decisions on display and manipulation options, such as, for example, read, post, or modify, can be established for objects of a level depending upon attributes set.

Example for Group Permissions In the following example herein, each group is assigned the following attributes or flags, as shown herein below in Table A:

Table A

The Read flag specifies that group documents may or may not be listed and readable by a specified category of a user (All, Department, Group).

The Post flag specifies that a user of specified category (All, Department, Group) may or may not post information into the group. The Modify flag specifies that a user of specified category (All, Department, Group) may or may not edit or modify existing information in the group.

In one implementation of the example cited herein above, group documents are listed if an appropriate category's read or modify flags are set. A group is listed only if at least one appropriate category's flag is set.

Global Administrative Settings

It is noted that global administrative settings allow control and management of the environment, such as, for example, management of physical constraints, requirements, or recommendations.

Example

In the example herein, the following are recommended:

• a definable kilobyte (KB) limit for the size of an image file uploaded;

• an option to upload a company logo; and

• an option to set an automatic logout time.

Main Components Fig. 2 is a block diagram showing the relationship of the main components according to the invention. A Web browser 200 is connected to a server 210 by a network connection 220. Associated with the server 210 is a back engine 230 for controlling the directory and document structure functions, and a storage 240 for saving modifications made by an end-user.

Accordingly, although the invention has been described in detail with reference to particular preferred embodiments, persons possessing ordinary skill in the art to which this invention pertains will appreciate that various modifications and enhancements may be made without departing from the spirit and scope of the claims that follow.

Claims

1. A system for an end-user to manipulate dynamically a level structure for at least one level on-line comprising: a Web browser from which said end-user performs level structure manipulation; a server; a network connection between said Web browser and said server; a back engine associated with said server and said Web browser for allowing said user to manipulate said level structure, and a storage associated with said back engine and said server for storing information associated with said level structure.

2. The system of Claim 1 , wherein said at least one level comprises at least one object.

3. The system of Claim 2, wherein said at least one object is a second level comprising at least one second object, wherein said at least one level is a nested level.

4. The system of Claim 1 , wherein said level is a directory or a document.

5. The system of Claim 1 , wherein said manipulation comprises, but is not limited to, adding, deleting, moving, copying, and renaming.

6. The system of Claim 1 , wherein said back engine uses an executable CGI module on said server to process requests from said end-user through said Web browser to change said level structure.

7. The system of Claim 3, wherein said level structure is highly organized and comprises a multi-level hierarchy model, said model comprising said nested levels.

8. The system of Claim 7, wherein said multi-level hierarchy model is a three-level hierarchy model comprising: a department level; a group level; and a document level.

9. The system of Claim 3, wherein each level has a set of permissions and administrators, wherein said administrators manage said permissions.

10. The system of Claim 8, wherein each department, group, and document level has a set of permissions, and wherein each department and each group level has administrators, wherein said administrators manage said permissions.

11. The system of Claim 9, wherein said end-user is a level administrator.

12. The system of Claim 1 , wherein said level comprises at least one area.

13. The system of Claim 8, wherein said group level comprises: a document area for containing documents prepared in a Web compatible editor; and a file area for containing uploaded files; wherein said end-user selects to view either a first list associated with said document area, a second list associated with said file area, or a list associated with both said document and file areas.

14. The system of Claim 13, wherein said storage stores content-type information about each of said uploaded files.

15. The system of Claim 13, wherein when any of said uploaded files has an associated icon and said any of said uploaded files is displayed, said associated icon is displayed on said Web browser.

16. The system of Claim 3, wherein said Web browser displays a list of said level structure, said list comprising said nested level, wherein when said end-user selects said nested level, a second list comprising said second level is displayed, and wherein if a previous second list is displayed, said previous second list is made not to be displayed.

17. The system of Claim 8, wherein said Web browser displays a list of departments, wherein when said end-user selects a department from said list of departments a list of groups is displayed, wherein when said end-user selects a group from said list of groups a list of documents is displayed, and wherein if a previous group list or a previous document list is displayed, said previous group list or said previous document list is made not to be displayed.

18. The system of Claim 16, wherein each of said list is displayed in a particular order.

19. The system of Claim 16, wherein when any of said lists is large, each of said large list is divided into several pages.

20. The system of Claim 9, further comprising a first top level administrator, actions of said top level administrator comprising any of, but not limited to: all actions of said end-user of said system; all actions of said level administrators; deleting any of said objects or levels; granting or revoking another top level administrator privileges, wherein said first top level administrator cannot revoke said first top level administrative privileges; granting or revoking level administration privileges; moving or copying said objects or levels; viewing system statistics, said statistics comprising, but not limited to: number of users; list of users; number of objects per associated level; and number of levels; adding new end-users; removing existing users; and locking or unlocking existing users.

21. The system of Claim 10, further comprising a first top level administrator, actions of said top level administrator comprising any of, but not limited to: all actions of said end-user of said system; all actions of said department and group administrators; deleting any of said departments or creating a new department; granting or revoking another top level administrator privileges, wherein said first top level administrator cannot revoke said first top level administrative privileges; granting or revoking department administration privileges; moving or copying said documents or uploaded files from a first department or from a first group to a second department or to a second group; viewing system statistics, said statistics comprising, but not limited to: number of users; list of users; number of documents per each department; number of documents per each group; number of departments; and number of groups per department; adding new end-users; removing existing users; and locking or unlocking existing users.

22. The system of Claim 9, wherein each of said level administrators can perform any of, but is not limited to: all actions as a member of said associated level; all actions said second level administrator can perform; granting a new level membership; revoking an existing level membership; creating a new second level or deleting an existing second level; granting or revoking second level administration privileges among level members; moving or copying said level objects; and viewing level statistics.

23. The system of Claim 10, wherein each of said department administrators can perform any of, but not limited to: all actions as a member of said department; all actions group administrators can perform, wherein each group is inside said administered department; granting a new department membership; revoking an existing department membership; creating a new group or deleting an existing group inside said department; granting or revoking group administration privileges among department members; moving or copying said documents or uploaded files from a first group to a second group; and viewing department statistics.

24. The system of Claim 10, wherein each of said group administrators can perform any of: all actions as a member of said group; granting a new group membership to a member of parent department; revoking an existing group membership from a current group member; deleting or modifying a document stored in said group; deleting or renaming an uploaded file stored in a file area of said group. changing access privileges of said group; and viewing end-user and document statistics in a scope of said group.

25. The system of Claim 9, wherein said level permissions comprise predefined attributes assigned to predefined categories.

26. The system of Claim 25, wherein said predefined attributes comprise, but are not limited to: read, post, and modify attributes; wherein said read attribute specifies if associated level objects are readable by a member of an associated predefined category of said predefined categories, wherein said post attribute specifies if said member can post information onto said associated level; and wherein said modify attribute specifies if said member category can modify information in said associated level.

27. The system of Claim 25, wherein said predefined categories comprise, but are not limited to: an all users category; a department members category; and a group members category.

28. The system of Claim 26, wherein said level objects are listed when said read or modify attributes of said associated predefined category are set.

29. The system of Claim 9, further comprising means for storing information to manage system logins, said permissions on said levels for said end-user, whereby ensuring said end-user performs functions on said levels only when authorized, and wherein said server does not give direct access to said stored information.

30. The system of Claim 11 , wherein said permissions further comprise, but are not limited to: a definable limit size of an uploaded file in kilobytes; an option to upload a company logo; and an option to set an automatic logout time.

31. A process for an end-user to manipulate dynamically a level structure for at least one level on-line comprising the steps of: providing a Web browser from which said end-user performs level structure manipulation; providing a server; providing a network connection between said Web browser and said server; providing a back engine associated with said server and said Web browser for allowing said user to manipulate said level structure, and providing a storage associated with said back engine and said server for storing information associated with said level structure.

32. The process of Claim 31 , wherein said at least one level comprises at least one object.

33. The process of Claim 32, wherein said at least one object is a second level comprising at least one second object, wherein said at least one level is a nested level.

34. The process of Claim 31 , wherein said level is a directory or a document.

35. The process of Claim 31 , wherein said manipulation comprises, but is not limited to, adding, deleting, moving, copying, and renaming.

36. The process of Claim 31 , wherein said back engine uses an executable CGI module on said server to process requests from said end-user through said Web browser to change said level structure.

37. The process of Claim 33, wherein said level structure is highly organized and comprises a multi-level hierarchy model, said model comprising said nested levels.

38. The process of Claim 37, wherein said multi-level hierarchy model is a three-level hierarchy model comprising: a department level; a group level; and a document level.

39. The process of Claim 33, wherein each level has a set of permissions and administrators, wherein said administrators manage said permissions.

40. The process of Claim 38, wherein each department, group, and document level has a set of permissions, and wherein each department and each group level has administrators, wherein said administrators manage said permissions.

41. The process of Claim 39, wherein said end-user is a level administrator.

42. The process of Claim 31 , wherein said level comprises at least one area.

43. The process of Claim 38, wherein said group level comprises: a document area for containing documents prepared in a Web compatible editor; and a file area for containing uploaded files; wherein said end-user selects to view either a first list associated with said document area, a second list associated with said file area, or a list associated with both said document and file areas.

44. The process of Claim 43, wherein said storage stores content-type information about each of said uploaded files.

45. The process of Claim 43, wherein when any of said uploaded files has an associated icon and said any of said uploaded files is displayed, said associated icon is displayed on said Web browser.

46. The process of Claim 33, wherein said Web browser displays a list of said level structure, said list comprising said nested level, wherein when said end-user selects said nested level, a second list comprising said second level is displayed, and wherein if a previous second list is displayed, said previous second list is made not to be displayed.

47. The process of Claim 38, wherein said Web browser displays a list of departments, wherein when said end-user selects a department from said list of departments a list of groups is displayed, wherein when said end-user selects a group from said list of groups a list of documents is displayed, and wherein if a previous group list or a previous document list is displayed, said previous group list or said previous document list is made not to be displayed.

48. The process of Claim 46, wherein each of said list is displayed in a particular order.

49. The process of Claim 46, wherein when any of said lists is large, each of said large list is divided into several pages.

50. The process of Claim 39, further comprising a first top level administrator, actions of said top level administrator comprising any of, but not limited to: all actions of said end-user of said system; all actions of said level administrators; deleting any of said objects or levels; granting or revoking another top level administrator privileges, wherein said first top level administrator cannot revoke said first top level administrative privileges; granting or revoking level administration privileges; moving or copying said objects or levels; viewing system statistics, said statistics comprising, but not limited to: number of users; list of users; number of objects per associated level; and number of levels; adding new end-users; removing existing users; and locking or unlocking existing users.

51. The process of Claim 40, further comprising a first top level administrator, actions of said top level administrator comprising any of, but not limited to: all actions of said end-user of said system; all actions of said department and group administrators; deleting any of said departments or creating a new department; granting or revoking another top level administrator privileges, wherein said first top level administrator cannot revoke said first top level administrative privileges; granting or revoking department administration privileges; moving or copying said documents or uploaded files from a first department or from a first group to a second department or to a second group; viewing system statistics, said statistics comprising, but not limited to: number of users; list of users; number of documents per each department; number of documents per each group; number of departments; and number of groups per department; adding new end-users; removing existing users; and locking or unlocking existing users.

52. The process of Claim 39, wherein each of said level administrators can perform any of, but is not limited to: all actions as a member of said associated level; all actions said second level administrator can perform; granting a new level membership; revoking an existing level membership; creating a new second level or deleting an existing second level; granting or revoking second level administration privileges among level members; moving or copying said level objects; and viewing level statistics.

53. The process of Claim 40, wherein each of said department administrators can perform any of, but is not limited to: all actions as a member of said department; all actions group administrators can perform, wherein each group is inside said administered department; granting a new department membership; revoking an existing department membership; creating a new group or deleting an existing group inside said department; granting or revoking group administration privileges among department members; moving or copying said documents or uploaded files from a first group to a second group; and viewing department statistics.

54. The process of Claim 40, wherein each of said group administrators can perform any of, but is not limited to: all actions as a member of said group; granting a new group membership to a member of parent department; revoking an existing group membership from a current group member; deleting or modifying a document stored in said group; deleting or renaming an uploaded file stored in a file area of said group, changing access privileges of said group; and viewing end-user and document statistics in a scope of said group.

55. The process of Claim 39, wherein said level permissions comprise predefined attributes assigned to predefined categories.

56. The process of Claim 55, wherein said predefined attributes comprise, but are not limited to: read, post, and modify attributes; wherein said read attribute specifies if associated level objects are readable by a member of an associated predefined category of said predefined categories, wherein said post attribute specifies if said member can post information onto said associated level; and wherein said modify attribute specifies if said member category can modify information in said associated level.

57. The process of Claim 55, wherein said predefined categories comprise, but are not limited to: an all users category; a department members category; and a group members category.

58. The process of Claim 56, wherein said level objects are listed when said read or modify attributes of said associated predefined category are set.

59. The process of Claim 39, further comprising the step of storing information to manage system logins, said permissions on said levels for said end-user, whereby ensuring said end-user performs functions on said levels only when authorized, and wherein said server does not give direct access to said stored information.

60. The process of Claim 41 , wherein said permissions further comprise, but are not limited to: a definable limit size of an uploaded file in kilobytes; an option to upload a company logo; and an option to set an automatic logout time.