> 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

Let Freelucy read the ServiceNow tables your users need to map.

YouDesign Freelucy is a scoped ServiceNow application. Freelucy does not enforce any cross-scope restrictions of its own — whether it can read a table is governed by ServiceNow's cross-scope access protection, which is a setting on the **target** table's application. Most ServiceNow tables don't enforce it, so Freelucy reads them out of the box. But when a table you need to map **enforces** cross-scope access, ServiceNow blocks Freelucy from reading it until you grant access with an **Application Cross-Scope Privilege**.

## When you need this

You only need a cross-scope privilege when a table you want to map enforces cross-scope access — Freelucy already reads tables that don't. The usual signs that a table is enforcing it:

* 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.
* A custom CI table you've added isn't readable in Freelucy.

***

## 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="info" %}
**On YouDesign Command?** If you're using the Visual Relationship Editor inside YouDesign Command (formerly UPM-X), set the application scope to **Command** instead of Freelucy.
{% endhint %}

***

## Step 2 — Create the cross-scope privilege

1. Click **All** and filter for **Application Cross-Scope**.
2. Open **Application Cross-Scope Access**. (Or go directly to the `sys_scope_privilege` table.)
3. Click **New**.
4. Fill in the new record:
   * **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.
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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/freelucy/configuration/cross-scope-privileges.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.