userManagement

In this section of the system configuration, which can be found in the instance-specific config/userManagement.xml file, the user management both of the editorial system and the live system can be configured. Furthermore the user preferences can be found here. The dictionary can have the following subentries:

  • editorial: Determines the properties of the user management of the editorial system.

  • live: Determines the properties of the user management of the live system.

  • preferences: In this dictionary the presets of user-specific configuration values for the GUI are stored. The Content Management Server uses these values if a user has not configured his individual settings. Except for the values contained in the guiPreferences entry, the settings refer to the GUI from NPS 5.2 and later if not stated otherwise. The dictionary kann have the following entries:

    • dateTimeInputFormatName: Date input format. Example: dayMonthYear

    • dateTimeOutputFormatName: Format of combined date and time output. Example: europeanShortDateTime.

    • defaultTemplate: The name of the master template to be used for the export and the preview. Default: mastertemplate.

    • displayTitleFormat: The format in which the value of the displayTitle parameter is returned. The parameter is used by the HTML user interface to find the title of the most entities to be displayed in the Content Manager (fields, file formats, workflows, etc.). %s can be used up to two times as a place-holder in the format string. The first instance of %s is replaced with the title of the respective entity (e.g. the title of a workflow), the second instance with the primary key (e.g. the name of a workflow).

    • guiPreferences: User-specific presets for the Content Navigator. The subelements are described in the section guiPreferences.

    • inputCharset: The default character set of the documents the user imports via Tcl (selectable as Standard character set when importing via the GUI).

    • languages: the languages preferred by the user. Each language is represented by a language element. The first element determines the language of the HTML user interface. Example:

      <languages type="list">
        <language>de</language>
        <language>en</language>
      </languages>
      
    • listDisplayRows: The number of lines in search result lists and in the file hierarchy display.

    • maxHierarchyDepth: The maximum number of levels to be displayed in the file hierarchy.

    • maxHierarchyLines: The maximum number of lines to be displayed in the file hierarchy.

    • preferEditedContents: Determines whether draft versions (YES) or released versions (NO) of files displayed in the preview are to be preferred. If YES is selected, the released version is only used if a file neither has a draft nor a committed version. If NO is selected a file is treated as if it were not present, if no it does not have a released version. This setting also affects the exportBlob of a version.

    • preferEditedTemplates: The same as preferEditedContents but for layout files. The setting also affects the visibleExportTemplates of files.

    • textAreaHeight: The height of multi-line text input fields.

    • textAreaWidth: Width of multi-line text input fields.

    • textFieldWidth: Width of single-line text input fields.

    • timeZone: The user-specific time zone setting. The list of time zone names can be retrieved using the systemConfig validTimeZoneNames Tcl command. Example: CET

  • globalPermissions: The value of this entry is a list of names of global permissions. Example:

    <globalPermissions type="list">
      <globalPermission>permissionGlobalRoot</globalPermission>
      <globalPermission>permissionGlobalUserEdit</globalPermission>
      <globalPermission>permissionGlobalUserAttributeEdit</globalPermission>
      <globalPermission>permissionGlobalRTCEdit</globalPermission>
      <globalPermission>permissionGlobalExport</globalPermission>
      <globalPermission>permissionGlobalMirrorHandling</globalPermission>
    </globalPermissions>
    

    You can define here additional permissions that can be used in the Content Management Server to restrict the use of file formats to particular user groups.