Inbound actions defined in the scoped application will not be able to access the objects defined in the global scope API. 

Objects such as current, email are defined in the global scope and trying to access them from a different scope will throw errors.

Inbound actions defined in the scoped application will not be able to access the objects defined in the global scope API. 

Objects such as current, email are defined in the global scope and trying to access them from a different scope will throw errors.

To resolve this issue you need to check the conditions and the action script of the inbound actions to see which objects of the global API are being accessed. 

Consider a sample inbound action which is accessing current, email objects.

To resolve the cross scope privilege issue with the above said sample inbound action we need to define below cross scope privileges from source scope(scope where we have inbound action created) to target scope(global).

** Please test in your sub-production instance first .

Below is how you can create:

Go to cog wheel settings at the top >> Go to Developer >> switch to the scoped application >> Go to Application Cross-Scope Access >> Click on New>>

Add the below cross scope privileges:

Select Target Scope as Global >> Target Name  as ScopedGlideElement >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update

Select Target Scope as Global >> Target Name as ScopedEmailWrapper >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update

Select Target Scope as Global >> Target Name as ScopedEmailLogger >> Target Type as Scriptable >> Operation as Execute API >> Status as Allowed >> Click on Update