Access to KPI Composer

  • Release version: Yokohama
  • Updated June 16, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Access to KPI Composer

    Access to KPI Composer controls whether a user can create, edit, or only view KPI Composer projects, as well as which projects they can access and whether they interact with the underlying records or just the user interface. Access is determined by user roles, assigned responsibilities, and project sharing settings.

    Show full answer Show less

    User Roles

    There are two primary roles that define access levels:

    • KPI Composer Admin (snkpicomposer.admin or admin, paviewer):
      • Full access to all KPI Composer components, projects, and records.
      • Can share projects and assign responsibilities.
      • Can associate indicator and breakdown definitions with Performance Analytics entities.
    • KPI Composer User (snkpicomposer.user):
      • Can only access projects they have created or those shared with them with appropriate rights.
      • Can share or assign responsibility only for projects they create.
      • Access is limited to design tabs, artifact properties, indicator and breakdown definitions.
      • Cannot add Performance Analytics indicators or breakdowns.
      • Additional Performance Analytics roles are required to implement designs.

    Responsibility for Projects

    Users assigned responsibility for a project have the ability to:

    • View and edit the project.
    • Share the project or assign responsibility to others.
    • Access design elements similar to a KPI Composer user but cannot add Performance Analytics indicators or breakdowns.

    This access level is role-independent and focuses on oversight and implementation. Responsible users are designated within project properties by users with edit rights.

    Shared Projects

    Projects can be shared with two levels of access:

    • Edit access: Equivalent to a responsible user or KPI Composer user without requiring a specific role, but does not imply responsibility for project oversight.
    • View access: Allows read-only access to project design tabs, artifact properties, and definitions. Users can use search and filter utilities and add journal entries but cannot modify the project.

    Practical Considerations for ServiceNow Customers

    Understanding these access levels helps you manage KPI Composer projects securely and efficiently by:

    • Assigning appropriate roles and responsibilities to control who can create, edit, or view projects.
    • Sharing projects with the right access level to balance collaboration and control.
    • Ensuring users have necessary Performance Analytics roles to fully implement KPI designs.

    By properly configuring access, you can maintain project integrity while enabling effective collaboration and oversight within KPI Composer.

    The level of access to KPI Composer determines whether a user can create, edit, or only view a KPI Composer project. It also determines which projects a user can access and whether they can access the underlying records or only the UI.

    Access to KPI Composer depends on the following things, singly or in combination:
    • User role
    • Responsibility
    • Access granted during sharing

    Role-based access

    An admin can grant a user the role of a KPI Composer admin or user. A KPI Composer admin has the same privileges as a ServiceNow AI Platform admin for KPI Composer. A KPI Composer user does not automatically have access to all projects and cannot associate indicator or breakdown definitions with actual Performance Analytics entities.
    Table 1. User roles for KPI Composer
    Role Contains Description
    sn_kpi_composer.admin or admin pa_viewer
    • Full access to all components of KPI Composer, including records.
    • Full access to all projects.
    • Can share or assign responsibility for projects.
    • Can associate indicator and breakdown definitions with Performance Analytics indicators and breakdowns.
    sn_kpi_composer.user None
    • Can access only projects that they have created.
    • Can share or assign responsibility for projects they create.
    • Can access only the design tabs, artifact properties, indicator definitions, and breakdown definitions of those projects.
    • Cannot add Performance Analytics indicators or breakdowns to the respective definitions.

    A user with this role may have access to more projects based on responsibility or on projects being shared with them.

    The appropriate Performance Analytics roles are also necessary to implement KPI Composer designs in Performance Analytics.

    Responsibility for projects

    A responsible user has the following access to the projects they are responsible for:
    • Can view and edit the projects.
    • Can share or assign responsibility for the projects.
    • Can access only the design tabs, artifact properties, indicator definitions, and breakdown definitions of those projects.
    • Cannot add Performance Analytics indicators or breakdowns to the respective definitions.

    This level of access is equivalent to what the sn_kpi_composer.user role grants. It is also equivalent to having a project shared with edit rights. Responsibility differs first in being independent of any role. The second difference is procedural, not technical: Responsible users are understood to be in charge of oversight and implementation of the project. Even the creator of a project is therefore not automatically responsible for it.

    Responsible users are named in the project properties. Any user with edit rights can name responsible users. For more information about naming responsible users, see Define properties for a project.

    Shared projects

    Any user with edit rights can share a project. When you share a project, you grant one of two levels of access:

    Edit access
    This level of access is technically the same as the access of a responsible user, or a user with the sn_kpi_composer.user role. The first difference is that no role is required. The second difference is that there is no implication of responsibility to oversee or implement the project.
    View access
    A user with view access can read the design tabs, artifact properties, indicator definitions, and breakdown definitions of the shared project. They can use all viewing utilities, like search and filter. However, they cannot change anything in the project. The only thing they can add is a journal entry.

    For more information, see Share a KPI Composer project.