• for setting up the catalogs to meet the needs of your workgroup. To find out how, see “Managing Catalogs” .

• for creating Cumulus Client users and giving them the permissions for accessing catalogs and functions as it best suits your workflow. To find out how, see “User Properties” .

• for providing View Sets, Asset Handling Sets, Actions, and Metadata Templates to the Cumulus Client users that meet the specific needs of your workgroup. To find out how to define these sets, see “Customizing Cumulus” .
The Cumulus Administrator can also give other Client users the permissions to define these items. You can have users with very individual permissions. For example, you can have users who have the permissions to define shared Asset Handling Sets or the permissions to define shared View Sets and others who are allowed to do both. This enables big organizations to delegate these tasks to different users, e.g. from different departments. However, as the Cumulus Administrator knows best about the fields included in the catalogs, it’s also the Cumulus Administrator who knows best how to set up View Sets that meet the specific needs of the workgroup and fit the catalogs used by the workgroup. Again it’s the Cumulus Administrator who knows best about the Asset Handling modules that are used by the workgroup and that’s why the Cumulus Administrator is the one who knows best how to set up Asset Handling Sets that are ideal for the workflow. The same goes for Actions and Metadata Templates. However, it is up to you either to take over these tasks yourself or to train other users so that they can take on these tasks.

• for configuring messages sent by the mail notification function. (For details, see “Configuring Email Notifications” )