--- sourceDocument: Australia Platform Analytics sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Access to KPI Composer # Access to KPI Composer {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 in ServiceNow Australia release controls a user's ability to create, edit, or view KPI Composer projects and their underlying records. Access is determined by user roles, project responsibilities, and sharing permissions, which together define what projects a user can access and what actions they can perform within those projects. Show full answer Show less ## Key Access Methods * **Role-Based Access:** Admins assign roles such as `snkpicomposer.admin` (or admin) and `snkpicomposer.user`. Admins have full access including editing and associating KPI Composer elements with Performance Analytics entities. Users with the user role have limited access---only to projects they create or those shared with them with edit rights, without the ability to link to Performance Analytics indicators or breakdowns. * **Responsibility for Projects:** Users designated as responsible for a project can view, edit, and share the project, similar to users with the `snkpicomposer.user` role, but responsibility is assigned explicitly within project properties. Responsible users oversee the project implementation, but responsibility is independent of any role assignment. * **Shared Projects:** Users with edit rights can share projects with others, granting either: * **Edit Access:** Equivalent to the access of a responsible user or `snkpicomposer.user` role, but without role requirements or responsibility implications. * **View Access:** Allows users to view all project components and use viewing utilities but restricts them from making changes except for adding journal entries. ## Practical Implications for ServiceNow Customers * Assign roles carefully to balance access and control; admins can fully manage KPI Composer, while users have scoped access. * Use project responsibility assignments to designate oversight without changing user roles, enabling clear project governance. * Leverage project sharing to extend collaboration with granular control: edit access for contributors and view access for stakeholders. * Ensure users have the required Performance Analytics roles to implement KPI Composer designs effectively. 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 {#access-to-kpi-composer__ul_lzm_pwp_p4b} ## Role-based access {#access-to-kpi-composer__section_kpi-comp-roles} 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.{#access-to-kpi-composer__table_wcd_bly_vjb__entry__3} | 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. {#access-to-kpi-composer__ul_u5p_dm5_p4b} | | 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. {#access-to-kpi-composer__ul_zpl_yl5_p4b} A user with this role may have access to more projects based on responsibility or on projects being shared with them. | [Table 1. User roles for KPI Composer] {#access-to-kpi-composer__table_wcd_bly_vjb} The appropriate Performance Analytics roles are also necessary to implement KPI Composer designs in Performance Analytics. ## Responsibility for projects {#access-to-kpi-composer__section_r5f_v1q_p4b} 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. {#access-to-kpi-composer__ul_responsible-access} 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](https://www.servicenow.com/docs/m8pOotZOMOmi_MbCqIyL~A "In the Project Properties, you can associate knowledge articles, owners, and contact persons with the project."). ## Shared projects {#access-to-kpi-composer__section_pc5_1cw_p4b} 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](https://www.servicenow.com/docs/syceoihyKwIzzCaRSDDrgQ "You can share a KPI Composer project that you own or that you are responsible for. You can provide the user with either read-write or read-only access.").