Manage cross-scope privileges

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

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.

On UPM-X? If you're using the Visual Relationship Editor inside UPM-X, set the application scope to UPM-X instead of Freelucy.

---

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 defined, it will appear in the table picker.

Want more depth? ServiceNow's documentation on Cross Scope Privileges covers the full mechanism, including write, create, and delete operations.

---

What's next

Continue with Manage suggested relationships.