> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/blueprints/start-here/roles-and-permissions.md).

# Roles and Permissions

Your role decides which actions show up and which screens you can work in.

If a button or menu item is missing, your role is usually the reason.

Blueprints roles are ServiceNow roles under the `x_inpi_ydbp` scope. They follow your instance's standard role assignment, ACL, and audit behavior.

## Role overview

| Role                      | Main purpose                        | Typical actions                                                                     |
| ------------------------- | ----------------------------------- | ----------------------------------------------------------------------------------- |
| Blueprint Template Editor | Define structure and governance     | Create templates, edit template rules, manage templates, create and edit blueprints |
| Blueprint Editor          | Build blueprint content             | Create blueprints, edit blueprint content, save/update blueprints                   |
| Blueprint Committer       | Review and publish approved changes | Open existing blueprints, review pending changes, run commit workflows              |
| Blueprint Viewer          | Read-only access                    | Open blueprints in Presenter Mode, review data and compliance without editing       |

## What each role can do

<table><thead><tr><th>Role</th><th width="258.74609375">Can</th><th>Cannot</th></tr></thead><tbody><tr><td>Blueprint Template Editor</td><td>Create and manage templates, configure tables/fields/filters/relationship rules, create and edit blueprints, open compliance and commit workflows, delete blueprints</td><td></td></tr><tr><td>Blueprint Editor</td><td>Create blueprints from templates, edit existing blueprints, save and update, duplicate blueprints, open compliance and commit workflows</td><td>Manage templates (unless also a Blueprint Template Editor)</td></tr><tr><td>Blueprint Committer</td><td>Open existing blueprints for review, access commit workflows, publish approved changes through Commit Changes</td><td>Create or edit blueprints, manage templates</td></tr><tr><td>Blueprint Viewer</td><td>Open blueprints in Presenter Mode, inspect blueprint details and compliance, use shared links safely</td><td>Create, edit, commit, or delete</td></tr></tbody></table>

## Important role-based behaviors

### Home page actions change by role

* **Manage Templates** appears only when your role allows template governance.
* **New Blueprint** appears only when your role allows blueprint creation.
* **Commit Changes** appears only when your role allows commit workflows.

### Opening a blueprint depends on your role

* Blueprint Template Editors, Blueprint Editors, and Blueprint Committers open the blueprint in the **Blueprint Editor**
* Blueprint Viewers open the same blueprint in **Presenter Mode**

### Delete permissions are stricter than edit permissions

* Blueprint Template Editors can delete blueprints
* Blueprint Editors can delete only blueprints they own
* Blueprint Viewers cannot delete blueprints

## Who sees which audit results

{% hint style="success" %}
**New in 26.1.** Applies to [Reviews](/blueprints/review-and-share/reviews.md) only.
{% endhint %}

Findings expose data quality problems on records you may not be entitled to see, so audit results are scoped to their audience.

| Role                      | Sees                                                                                                                                              |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Blueprint Template Editor | Every finding, run, trend and schedule                                                                                                            |
| Everyone else             | Findings assigned to them or to one of their groups, findings on schedules they are informed about, and trends for templates they have a stake in |

A scoped reader is told the list is limited, so a short list does not read as a healthy estate.

This is enforced by the application, not merely hidden. Access to the underlying record is checked separately: a finding on a record you cannot read is withheld, and the count of withheld rows is shown rather than the list silently being short.

### Configuring audits is a template-editor action

Creating or editing a schedule, and starting a run by hand, require the **Blueprint Template Editor** role.

Blueprint Editors can open the Schedules tab and see the schedules they are informed about. The create, edit and run controls are not shown to them, and the page says which role is needed rather than leaving a page with no buttons and no explanation.

## Where to check your current role

On Home, open your user avatar menu. The app shows the Blueprints roles currently assigned to you.

## When something looks wrong

If you expected to see an action and it is missing:

1. Check your role in the avatar menu
2. Refresh the app if your access was changed recently
3. Contact your ServiceNow administrator if the role assignment still looks incorrect


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ins-pi.com/blueprints/start-here/roles-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.