Triggers: Difference between revisions

66 bytes removed ,  20 September 2016
m
no edit summary
mNo edit summary
mNo edit summary
Line 27: Line 27:


== Security ==
== Security ==
Some features available from scripts (file operations, the implementation of http-requests, access to other libraries) for safety reasons requires a permit. These permissions a user must manually set separately for each library.
Since the scripts have access to more actions than a user does, they require additional permissions.


To open the dialogue set permissions for scripts — open library triggers list and click Shield on the toolbar. Set permissions must be done on each device separately. Selected resolution is not synchronized between devices.
The user must define these permissions manually for each library.


=== Permissions scripts ===
To open the dialog to set permissions for scripts — open library triggers list and click ''Shield'' on the toolbar. Permissions must be set separately on each device. Permissions are not synchronized between devices.
 
=== Permissions for scripts ===
; Libraries
; Libraries
: Determines which libraries will be available in addition to the native script. You can grant access to all libraries, or select certain libraries. This authorization is required for libByName function.
: determines which other libraries can be affected by the script. You can grant access to all libraries or select only certain libraries. This authorization is required for the libByName function.
 
-----
; Read files
; Read files
: It provides access to the script file read from the storage device. This authorization is required for file functions.
: It provides access to the script file read from the storage device. This authorization is required for file functions.