> 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/freelucy/configuration/grant-access.md).

# Grant access to users

YouDesign Freelucy ships with two roles. Assign them through standard ServiceNow user administration, to individual users or, preferably, to groups.

## The two roles

<table><thead><tr><th width="104.55434487760067">Role</th><th>Technical name</th><th width="118.27309440262616">Inherits</th><th>What it allows</th></tr></thead><tbody><tr><td>Editor</td><td><code>x_inpgh_lucy.editor</code></td><td>Reader</td><td>Create, remap, and delete relationships, and commit changes.</td></tr><tr><td>Reader</td><td><code>x_inpgh_lucy.reader</code></td><td>None</td><td>View existing relationships of a CI in read-only mode.</td></tr></tbody></table>

The Editor role contains the Reader role, so you only ever need to assign one or the other, not both.

{% hint style="info" %}
**What Reader users see.** A Reader opens Freelucy in read-only mode. They can browse the record across all views, inspect relationships, and jump between records, but the add, remap, remove, and commit actions are not available to them.
{% endhint %}

***

## Assign a role to a group (recommended)

{% hint style="success" %}
**Best practice.** Assign roles to groups, not individual users. It scales better and survives team changes without manual cleanup.
{% endhint %}

1. From the ServiceNow homepage, click **All** and filter for **User Administration**, then open **Groups**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-grant-access-groups.png</code></strong> Open Groups under User Administration.</p></div>
2. Open the group that should receive Freelucy access.
3. On the **Roles** tab, click **Edit**.
4. Filter by `x_inpgh_lucy` and select **Editor** or **Reader**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-grant-access-filter-roles.png</code></strong> Filter for the Freelucy roles and select Editor or Reader.</p></div>
5. Click the right arrow to add the role to the Roles List.
6. Click **Save**.

***

## Assign a role to an individual user

Use this only when group-based assignment is not appropriate, for example a one-off pilot user.

1. From the ServiceNow homepage, click **All** and filter for **User Administration**, then open **Users**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-grant-access-users.png</code></strong> Open Users under User Administration.</p></div>
2. Open the user record.
3. On the **Roles** tab, click **Edit**.
4. Filter by `x_inpgh_lucy` and select the role.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-grant-access-user-role.png</code></strong> Filter for the Freelucy roles on a user record.</p></div>
5. Click the right arrow to add the role to the Roles List.
6. Click **Save**.

***

## What's next

Continue with [Manage cross-scope privileges](/freelucy/configuration/cross-scope-privileges.md).


---

# 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:

```
GET https://docs.ins-pi.com/freelucy/configuration/grant-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
