› Access KCM Designer

Access KCM Designer

Functionality in KCM Designer is organized according to roles. Each user is assigned a role depending on a task in the project (see Common starting points). Every role comes with a set of permissions. For instance, a Project Administrator is able to grant a template designer access to the project to edit Text Blocks, and so on.

Typically, KCM Designer is integrated into a business application of the organization. A user may not need to log on. In case KCM Designer remains unintegrated, the user receives credentials to log on from a system administrator.

If the installation is successful, a predefined project called "InstallationTest" appears after a user logs on. Several usage examples in this guide are based on the predefined project, which is intended for testing and training purposes. You can delete the project using KCM Designer for Windows.

KCM Designer has a limited support for the projects created prior to KCM 4.0 and shows warning messages for such projects.

Roles and permissions

KCM Designer comes with the following roles and corresponding permissions:

  • Author: Delete, Edit, New, Rename, Set Description, Test, Unlock, Submit for review, View.

    However, an Author cannot perform these actions on Master Templates, Libraries, Includes, Data Backbone, brands, as well as on Style Sheets and Page Style documents for brands.

  • Content Reviewer: Accept, Reject, Test, View.
  • Publisher: Publish, Reject, Test, View.
  • Publishing Author: Granted permissions for both an Author and a Publisher.
  • Publishing Reviewer: Granted permissions for both a Content Reviewer and a Publisher.
  • Viewer: View.
  • Project Administrator: In addition to all permissions mentioned above, the Project Administrator has the Retract Approval permission and can grant access to other users.

In KCM Designer, you cannot create new roles.

In general, the following rules apply to all permissions:

  • Roles and corresponding permissions can only be granted to users through the assignment of roles.
  • No permission is granted by default.
  • Permissions are granted in all cases where an action is relevant.