Arctera™ Insight Surveillance User Guide
- Introducing Arctera Insight Surveillance
- Getting started
- Working with dashboard widgets
- Managing employee groups
- Managing departments
- About departments
- Understanding the Departments page
- Searching departments
- Creating departments
- Moving existing departments under other departments
- Adding monitored employees and employee groups to departments
- Editing monitoring policies
- Editing department details and monitoring policy
- Managing exception employees
- Designating employees as exception employee
- Assigning further exception reviewers to an exception employee
- Removing exception status
- Removing exception reviewers
- Managing department users
- Managing department-level searches
- Managing department-specific hotword sets
- Managing department-specific labels
- Managing department-specific trash rules
- Managing department-specific allowlist rules
- Managing department-specific review comments
- Viewing employees associated with departments
- Managing users, roles, and permissions
- Overview
- Predefined user roles and permissions
- Adding new roles for users (employees) and employee groups
- Editing user roles and permissions
- Deleting user roles
- Assigning Insight Surveillances to users (employees) and employee groups
- Restricting users to use hotwords in searches
- Removing a user role
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific trash rules
- Managing application-specific allowlist rules
- Managing application-specific review comments
- Managing data requests
- Managing search schedules
- Managing export operations
- Managing reviews
- About reviewing with Insight Surveillance
- Limitations on reviewing certain types of Skype for Business content
- Understanding the Review page
- Changing the Preview pane position
- Rearranging columns in the item list pane
- Customizing item navigation in Review grid
- Filtering the items in the Review pane
- Viewing dynamic review item counts on the calendar
- Reviewing the Audio-Video Transcript type items
- Reviewing searched items
- Translating email and attachment content for review
- Translating collaboration message for review
- Adding or removing text for machine learning
- Assigning review status to items
- Viewing hotwords highlighting
- Viewing hotwords in collaboration message
- Viewing tags highlighting
- Viewing predicted labels of review items
- Viewing the full content in a new window
- Adding comments to items
- Escalating the review items
- Applying labels to items
- Viewing history of items
- Printing and downloading the items and attachments
- Viewing Intelligent Review Details
- Working with reports
- About Insight Surveillance reports
- Predefined reports
- Enhanced reporting
- Configuring a reporting endpoint
- Authentication
- Departments API
- Users API
- Roles API
- User Roles Async API
- User Roles API
- Classification Tags API
- Labels API
- Searches API
- ItemMetrics API
- Reviewer Mapping Async API
- Reviewer Mapping API
- MonitoredEmployees API
- Evidence Of Review Async API
- Evidence of Review API
- Item Classification Metrics Async API
- Item Classification Metrics API
- Item Label Metrics Async API
- Item Label Metrics API
- Item Archived Metrics Async API
- Item Archived Metrics API
- Item Hotword Metrics Async API
- Item Hotword Metrics API
- Item Details Async API
- Item Details API
- Reviewer Assessment Metrics Async API
- Reviewer Assessment Metrics API
- Report Status API
- Supported OData query options
- Supported reporting endpoint API filters and their values
- Responses
- Managing Power BI templates for reporting APIs
- Accessing Insight Surveillance reports and datasets through the OData web service
- Guidelines for using Insight Surveillance templates with Microsoft Power BI Desktop
- TEMPLATE - Departments, Users, Roles, Labels
- TEMPLATE - User Roles - Submit Report Request
- TEMPLATE - User Roles - View Report Data
- TEMPLATE - Item Metrics
- TEMPLATE - Reviewer Mapping - Submit Report Request
- TEMPLATE - Reviewer Mapping - View Report Data
- TEMPLATE - Searches
- TEMPLATE- Item Classification Metrics - Submit Report Request
- TEMPLATE- Item Classification Metrics - View Report Data
- TEMPLATE- Item Archived Metrics - Submit Report Request
- TEMPLATE- Item Archived Metrics - View Report Data
- TEMPLATE- Item Label Metrics - Submit Report Request
- TEMPLATE- Item Label Metrics By Employee - View Report Data
- TEMPLATE- Item Label Metrics By Department - View Report Data
- TEMPLATE- Item Hotword Metrics - Submit Report Request
- TEMPLATE- Item Hotword Metrics - View Report Data
- TEMPLATE- Item Details - Submit Report Request
- TEMPLATE- Item Details - View Report Data
- TEMPLATE- Reviewer Assessment Metrics - Submit Report Request
- TEMPLATE- Reviewer Assessment Metrics - View Report Data
- TEMPLATE- Evidence Of Review - Submit Report Request
- TEMPLATE- Evidence Of Review By Monitored Employee - View Report Data
- TEMPLATE- Evidence Of Review By Department - View Report Data
- TEMPLATE- Evidence Of Review With Item Archived Metrics - Submit Report Request
- TEMPLATE- Evidence Of Review With Item Archived Metrics - View Report Data
- Saving, editing, and refreshing the Power BI reports
- Managing Audit Settings
- Working with Audit viewer
Authentication
To ensure the security and integrity of data access, the Reporting API requires authentication. Authentication is used to verify the identity of the requesting client or application and determine whether it has the necessary permissions to access the API resources. There are two primary authentication methods supported for this API:
Upon configuring the reporting endpoint API, a Base URL, a primary and secondary API Keys are generated. Include either primary or secondary API key in the header of your API requests.
For example,
X-API-Key:<Primary or Secondary API Key>
Basic Authentication is a method where API clients provide a username and password with each request. Users use an encoded string in the Authorization header for this method. The recipient of the request uses this string to verify the users' identity and their access rights to a resource.
For example,
Authorization: Basic <Base64 encoded credentials>
To generate a Base64 encoded credentials:
Combine the credentials (username and password) with a colon (:).
Note:
The username must be . The password can be either a primary or a secondary API Key provided after configuring the reporting endpoint. Use either one as your password.
For example, ReportingApiUser:32adasdf3asdcvzxcweasd
After specifying the credentials as mentioned in the step above, generate a Base64 encoded credentials. It is required while setting authorization header.
For example, dGVuYW50OmtleQ==
Therefore, requests made by this user would be sent with the following header:
Authorization: Basic dGVuYW50OmtleQ==
When a server receives this request, it can access the Authorization header, decode the credentials, and look up the user to determine whether access to the requested resource should be allowed.