Access to KPI Composer
Summarize
Summary of Access to KPI Composer
Access to KPI Composer in ServiceNow determines whether a user can create, edit, or only view KPI Composer projects. It also controls which projects a user can access and whether they can interact with the underlying records or just the user interface. Access is governed by user roles, project responsibilities, and sharing permissions.
Show less
User Roles and Their Capabilities
- KPI Composer Admin (snkpicomposer.admin or admin, paviewer): Has full access to all KPI Composer components and projects, including the ability to share projects, assign responsibilities, and link indicator and breakdown definitions with Performance Analytics entities.
- KPI Composer User (snkpicomposer.user): Limited to accessing projects they created or those shared with them with edit rights. Can edit design tabs, artifact properties, indicator and breakdown definitions but cannot add Performance Analytics indicators or breakdowns. Additional Performance Analytics roles are required to implement KPI Composer designs in Performance Analytics.
Responsibility for Projects
Users assigned as responsible for a project can view, edit, share, and assign responsibility for that project. Their access level is equivalent to the snkpicomposer.user role but does not require that specific role. Being responsible implies oversight and implementation duties, which is a procedural distinction rather than a technical one. Responsible users are designated in project properties, and any user with edit rights can assign responsibility.
Shared Project Access
- Edit Access: Equivalent to the access of a responsible user or KPI Composer user role but does not confer responsibility. No specific role is required to have this access.
- View Access: Allows users to read design tabs, artifact properties, indicator and breakdown definitions, and use viewing utilities like search and filter. Users cannot make changes but can add journal entries.
Practical Implications for ServiceNow Customers
Understanding these access levels helps you manage who can create, modify, oversee, and view KPI Composer projects within your organization. Assign roles thoughtfully based on user responsibilities to ensure proper governance and collaboration. Use project sharing to extend access without changing roles, and designate responsible users to clarify project ownership and accountability.
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.
- User role
- Responsibility
- Access granted during sharing
Role-based access
| Role | Contains | Description |
|---|---|---|
| sn_kpi_composer.admin or admin | pa_viewer |
|
| sn_kpi_composer.user | None |
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
- 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.