multi user application software

 Multi-User

1. Multi-user software is software that allows access by multiple users of a computer. Time sharing systems are multi-user systems.

2. Most batch processing systems for mainframe computers may also be considered "multi-user", to avoid leaving the CPU idle while it waits for I/O operations to complete.

3. However, the term "multitasking" is more common in this context.
4. An example is a Unix server where multiple remote users have access (such as via a serial port or Secure Shell) to the Unix shell prompt at the same time. Another example uses multiple X Window sessions spread across multiple terminals powered by a single machine - this is an example of the use of thin client. Similar functions were also available under MP/M, Concurrent DOS, Multiuser DOS and FlexOS.

5. Some multi-user operating systems such as Windows versions from the Windows NT family support simultaneous access by multiple users (for example, via Remote Desktop Connection) as well as the ability for a user to disconnect from a local session while leaving processes running (doing work on their behalf) while another user logs into and uses the system. The operating system provides isolation of each user's processes from other users, while enabling them to execute concurrently [dubious – discuss].

6. Management systems are implicitly designed to be used by multiple users, typically one system administrator or more and an end-user community.

7. [The complementary term, single-user, is most commonly used when talking about an operating system being usable only by one person at a time, or in reference to a single-user software license agreement. Multi-user operating systems such as Unix sometimes have a single user mode or run level available for emergency maintenance

8. If you want the software to function as a multi-user application but you're not ready to establish the IT infrastructure and support required for a more robust database platform, you can place any standard repository file in a network location that's accessible by other users. With this configuration, you can Assign different permissions per user and/or per analysis. For example, a particular user might have read/write access to all projects owned by her department, read- only access to projects owned by other departments, and no access at all to projects designated "confidential."

10. Use configurable categories to manage analysis projects. Authorized users can establish categories and sub-categories that are used to organize a large number of analysis projects stored together in the same shared repository.