Arctera™ Insight Capture Configuration Guide
- INTRODUCTION
- DASHBOARD
- IMPORTERS
- File-Based Collector Options
- Amazon S3
- Audio Video
- BlackBerry
- Bloomberg
- Box
- CellTrust
- Chatter
- Chatter Cipher Cloud
- Cisco Webex Teams
- Citrix Workspace & ShareFile
- Dropbox Business
- Dubber Speik Recordings
- Dubber Speik SMS
- EML
- EWS
- Exchange Graph API
- FX Connect
- Google Drive
- IceChat
- JSON
- LSEG (Refinitiv)
- Microsoft Teams
- Microsoft Teams via Webhooks
- NTR-X
- OneDrive for Business
- Pivot
- Redtail Speak
- RingCentral
- ServiceNow
- SharePoint
- Slack eDiscovery
- Symphony
- Text-Delimited
- X (Twitter)
- UBS
- Web Page Capture
- Workplace from Facebook
- XIP
- XSLT/XML
- Verint
- Viva Engage (Yammer)
- Yieldbroker
- YouTube
- Zoom Chat
- Zoom Meetings
- Zoom Meetings Chats
- Zoom Meetings via Archiving API
- MONITORED USERS
- FILTERS
- TARGETS
- SETTINGS
- REPORTS
- APPENDIX
Notes
Attachments are not captured in the following cases:
If the shared file has restrictions such as an expired link, password protection, or access limitations.
If the file was shared and then deleted.
If a file's link was shared but the site where the file is located has undergone changes.
If messages are GDPR hard deleted, the attachments (if it has any) cannot be captured due to the source limitation.
A dummy SMTP address is created for a deleted message which is missing the deleted_by_id field.
GDPR hard deleted and soft deleted messages are captured as deleted. Legal Hold should be enabled so the attachments are not deleted from the SharePoint site.
When sharing an already existing file from SharePoint, the attachment will not be captured - only the URL of that attachment will be retrieved.
The created message does not say it was deleted from Viva Engage (Yammer). To capture the deletes, the data retention setting needs to be set to Delete. See instructions at Manage Viva Engage (Yammer) Data Compliance.
Events of former members are not captured due to limited permissions of admin-generated token.
For files larger than 2 GB, a link for that attachment will be created and included in the body of the output message with a warning in the log that the file is larger than 2 GB.
A separate Import folder path should be provisioned on the Source Configuration tab for each Viva Engage (Yammer) collector when running 2 or more collectors simultaneously.
Currently, enabling the Merge messages by thread feature may impact the performance of the collector processing.