DESelect is delivered as a Marketing Cloud Installed Package, which can be installed through a one-click installation link.
This Installed Package comes with certain permissions, called a scope. The scope determines what
DESelect is allowed to do through the API. The scope required for DESelect is minimal, with only the
permissions listed below. Note that the installed package already comes with these permissions, you
don’t need to take any additional steps. The scope is just explained below so you can understand why each scope is needed.
Offline Access: 60 days
DESelect needs to be able to:
- Follow up on the progress of SQL queries (query activities) a user has started, even if the user
has signed off
- Automatically refresh picklist values, which typically happens at night when no users are logged in. For this refresh, a query needs to run.
--> To ensure these activities can be performed, Offline Access is set to 60 days so a user's token (which is stored encrypted) so DESelect can perform these actions even if the user is not logged in to DESelect at that time.
Automations: Read, Write, Execute
DESelect needs to be able to:
- Create and update SQL queries
- Schedule executions of selections
Journeys: Read, Write, Execute, Activate/Stop/Pause/Resume/Send/Schedule, Delete
Required for features planned to be released in the near future.
Data Extensions: Read, Write
DESelect needs to be able to:
- Show a list of all data extensions
- Get the fields of a data extension
- Create new data extensions to write results of SQL queries to
- Write the results of a query to a data extension
Comments
0 comments
Please sign in to leave a comment.