Employee Document Sharing In this scenario, Company A has installed Nexus on a private web server that is accessible only to employees in the building and perhaps those who connect via VPN. Company A wants to give users the ability to find important human resources documents and forms that they will need during the tenure at Company A. But rather than putting everything in folder on one of their file servers, they decide that they want users to be able to do text searches for the documents. Once Nexus is installed, a single organization is created under which several groups are created - groups such as Sales, Marketing, Engineering, Human Resources, etc. The Human Resources department wants to give other employees access to a Health Insurance form. The HR user drags the form onto the FileBox. They then notify the administrator that they want to have this document become a permanent part of the Nexus library and that it should be made available to everyone. The administrator browses through the documents in the HR user's FileBox, finds the Health Insurance form and quickly copies it to the library in the 'Human Resources' category. Later, a user interested in changing Health Insurance options goes navigates to Nexus. The user knows that the document is related to health insurance so the user types 'Insurance' into the global find box. Nexus displays the Health Insurance document recently added along with other Insurance related documents. Client Document Sharing In this scenario, Company A produces graphic designs for a variety of clients. Once design drafts are created, they must be shown to the client. These drafts are often updated as changes are requested by the client. The drafts themselves are often very large image files. Nexus has been installed on a public web host. The administrator of the Nexus library has created a separate organization for each company that Company A deals with. Under each organization, a 'Primary Contacts' group has been created. One of the companies for which a design is being created is Alliance Architecture, Inc. Alliance Architecture is developing a website which Company A has been hired to design and build. During the design process, Company A designers create a couple of design ideas for which mockups are created. Rather than emailing these designs to a contact at Alliance, they post the images to the Nexus library under the Mockups category and provide and allow access to the 'Primary Contacts' group under the 'Alliance Architecture' organization. Primary contact Joe at Alliance Architecture logs into Nexus and browses through the mockups picking out the ones he likes best. |
|
Nexus Documentation > Overview >
Use Cases |