...
To access Exchange to browse content, you need the View version of the Exchange permission. However, you need to Manage version of both the Exchange permission and the corresponding resource type (Activeboards, alert configuration, lookups, or synthetic data) to be able to install/uninstall content in your domain.
However, certain content types have specific permissions in Devo that are also required for their installation/uninstallation via Exchange (Activeboards, Alert configuration, Lookups, and Synthetic data).
To know more about how to assign permissions to roles, visit the following article: Managing roles.
...
The error will be notified via message at the top right and the content related to the component affected will be visible but not accessible (neither open it nor install/uninstall it). In that case, you can freely navigate through the rest of the content without any risk of malfunctioning.
...
Exchange activity registry
Every action performed inside Exchange is registered in the devo.internal.audit.logs table for audit purposes. This table collects information from all the areas of the Devo platform but the fields explained below are the specific pieces concerning specifically to Exchange (visit this article for the complete table description):
Field | Data type | Description |
|---|---|---|
service |
| Name of the service or application where the action was executed, in this case: → Exchange. |
section |
| Name of the specific part inside the service where the action was executed. It corresponds to the different categories and technologies to navigate: → search, discover, allContent, forYou, mitre, useCase&data, Security, AWS, Crowdstrike, Monitoring, Authentication, Windows, Firewall, and ITOps. |
subsection |
| Name of the specific part inside the section where the action was executed. It corresponds to the sections inside the Discover category or the options to filter content by type in the rest of the categories: → Highlights, Featured, Trending, Newest, and RecentlyVisited. → all, app, Activeboard, alert, lookup, synthetic_data, pack, and use_case. |
object_name |
| Name of the specific content, for example: → Alert pack: Firewall |
action |
| Description of the action executed. For example: → get catalog, retrieve item, open, open content, update content, launch content, stop content, view content, install content, uninstall content, etc. |