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.
Click the globe icon at the top right of the menu bar.
Open Application scope and filter for Freelucy.
Select Freelucy.
Step 2 — Create the cross-scope privilege
Click All and filter for Application Cross-Scope.
Open Application Cross-Scope Access. (Or go directly to the
sys_scope_privilegetable.)Click New.
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.
Set Status to Allowed.
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.
What's next
Continue with Manage suggested relationships.
Last updated