> 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/cross-scope-privileges.md).

# Manage cross-scope privileges

YouDesign Freelucy is a scoped ServiceNow application. Out of the box, it has cross-scope read access to the most common ServiceNow tables. For any table that's not covered — including custom tables — you grant access manually with an Application Cross-Scope Privilege.

## When you need this

You need to add a cross-scope privilege whenever:

* A table you want to map relationships on doesn't appear in Freelucy's table picker.
* Freelucy returns an empty result when you know records exist on a table.
* You've added a new custom CI table since the last Freelucy update.

***

## Step 1 — Set the application scope to Freelucy

Cross-scope privileges are created in the scope of the consumer application — Freelucy.

1. Click the **globe icon** at the top right of the menu bar.
2. Open **Application scope** and filter for **Freelucy**.
3. Select **Freelucy**.

{% hint style="warning" %}
🖼️ **Screenshot needed — `v26-cross-scope-01.png`** Switch the application scope to Freelucy.
{% endhint %}

{% hint style="info" %}
**On UPM-X?** If you're using the Visual Relationship Editor inside UPM-X, set the application scope to **UPM-X** instead of Freelucy.
{% endhint %}

***

## Step 2 — Create the cross-scope privilege

1. Click **All** and filter for **Application Cross-Scope**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-cross-scope-02.png</code></strong> Find Application Cross-Scope Access.</p></div>
2. Open **Application Cross-Scope Access**. (Or go directly to the `sys_scope_privilege` table.)
3. Click **New**.
4. Fill in the new record:

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-cross-scope-03.png</code></strong> New Application Cross-Scope Privilege record.</p></div>

   * **Target name** — the technical name of the table you want Freelucy to access.
   * **Operation** — choose **Read**. This lets Freelucy read all records on the target table.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>🖼️ <strong>Screenshot needed — <code>v26-cross-scope-04.png</code></strong> Select Read as the operation.</p></div>
5. Set **Status** to **Allowed**.
6. Save.

Freelucy can now read records from that table. If the table also has a [suggested relationship](/freelucy/configuration/suggested-relationships.md) defined, it will appear in the table picker.

{% hint style="info" %}
**Want more depth?** ServiceNow's documentation on [Cross Scope Privileges](https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/reference/c_CrossScopePrivilegeRecord.html) covers the full mechanism, including write, create, and delete operations.
{% endhint %}

***

## What's next

Continue with [Manage suggested relationships](/freelucy/configuration/suggested-relationships.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/cross-scope-privileges.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.
