When you create a desktop, you determine what users can see and do when they log on to the web client.
Desktops are similar to teamspaces in that you specify what users can access when they are locating the content they need. For example, you can specify how the desktop functions by configuring the toolbars and menus that users can see and use to work with content. In teamspaces, you specify the folders and searches that users can access to find content. However, teamspaces provide a focused view of the relevant documents, folders, and searches that a team needs to complete tasks. Desktops can provide a broad view, but users might not be allowed to access specific features.
If you want to use IBM® Content Navigator from a mobile device, it is recommended that you configure some or all of the desktops in your environment to be accessed by the mobile application. When you configure a desktop to be accessed by the mobile application, you can specify which features users can access and which actions users can take. For example, you can prevent users from adding photos or documents from their mobile devices.
The layout of a desktop describes how the features of the desktop are arranged and the features that are available on the desktop. IBM Content Navigator includes a default layout; however, you can create plug-ins to define custom layouts.
When you configure the layout, you can specify which features users can access from the desktop and which feature is open when users log in to the desktop. For example, if you do not want users to browse the repository, you can exclude that feature from the desktop. If you expect users to work with specific documents rather than running frequent searches, you can set Home as the default feature.
In addition, you can configure the view and some of the toolbars that are available on the desktop.
The menus for the different toolbars and context menus that users access from the desktop are defined in the default menus that are provided by IBM Content Navigator. The menus determine the actions that users can do when they are working with items from the desktop. For example, a context menu that is available from a document might include the following actions: open, preview, delete, and check out. You can customize the menus to include only options that users need. You customize the contents of the menus in the Menus section of the administration tool. You can also create new types of menus by creating a plug-in.
When desktops are assigned to multiple repositories, the context menu that is accessed from the global toolbar is synchronized with the repository that is being used. If users are in the Favorites, Teamspaces, or Work views, they must review the repository name to confirm that they are adding content to the correct repository.
When you configure workflows for a desktop, you select the Process Engine application spaces that users can access from the desktop. Application spaces contain the resources for a workflow, such as the roles of users that are participating in the workflow. Application spaces also identify the list of users who are members of the role and the in-baskets that provide a view of items in a work queue. You must use the Process Engine or Process Configuration Console to define application spaces.
By default, all of the application spaces that are defined for a repository are available to users from the desktop. When you specify an application space, only that application space is available to users from the desktop for a specific repository.