...
Security - if you are evaluating the App, you can grant permissions to everyone or restrict access by assigning security roles to users or user groups.
Task - specify which fields will be synchronized when using the App. Each task has a start and end date and it can be mapped to different fields. If you are already using date fields in Jira (such as "Due date") simply map them and the App will use those dates during the synchronization to generate the tasks correctly.
Note
...
The start and end dates are required by the App to generate the task on the timeline. When tasks without date estimates are synchronized, the App will use the "Creation date" as both the start and end date mapped field values. If the task dependencies are defined this might result in unintentional updates of schedules.
Besides the task field mapping, we recommend disabling the comments and notifications. While they are very useful and improve communication, when you create your Boxes and synchronize existing data, users might receive numerous notification emails. Enable these features once your Boxes are synchronized.
Dependency configuration - like with the task field mapping, you can synchronize up to five different dependency types to visualize the task relationships.
Team field configuration - Teams are a very important element, especially when using the Board and Resources modules. Make sure to select the fields used for Team assignment.
Risks - check if the Risk heat map matches your organization's needs - change the field mapping or update the select options if required.
...