Veritas™ Surveillance User Guide
- Introducing Veritas Surveillance
- About Veritas Surveillance
- Key features of Veritas Surveillance
- Feature comparison: Compliance Accelerator desktop client Vs Veritas Surveillance web client
- Sampling support for content sources
- About Veritas Surveillance system security
- Veritas Surveillance multi-tier architecture
- System requirements
- Getting started
- Working with dashboard widgets
- Managing employees and 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
- Closing or opening the departments for monitoring
- Deleting departments
- Managing department users
- Managing department-level archives
- Managing department-level searches
- About department-level searches
- Guidelines for effective searches
- Creating and running department-level searches
- Pausing and resuming searches
- Downloading search details for archives
- Disabling scheduled searches
- Previewing search results
- Accepting search results
- Rejecting a search result
- Resubmitting a search
- Managing department-specific hotword sets
- Managing department-specific labels
- 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 Veritas Surveillances to users (employees) and employee groups
- Restricting users to use hotwords in searches
- Removing a user role
- Managing application-level archives
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific review comments
- Managing search schedules
- Managing export operations
- Managing reviews
- About reviewing with Veritas Surveillance
- Understanding the Review page
- Rearranging columns in the item list pane
- Changing the Preview pane position
- Filtering the items in the Review pane
- Reviewing the Audio-Video Transcript type items
- Reviewing searched items
- Viewing Intelligent Review Details
- Adding or removing text for machine learning
- Assigning review status to items
- Viewing hotwords highlighting
- Viewing hotwords in collaboration message
- Viewing tags highlighting
- Viewing tags in collaboration message
- Viewing the full content in a new window
- Adding comments to items
- Escalating the review items
- Viewing history of items
- Printing and downloading the items and attachments
- Working with reports
- About Veritas Surveillance reports
- Accessing data through the Microsoft SQL Server Reporting Services (SSRS)
- Enhanced reporting
- Configuring a reporting endpoint
- Authentication
- Departments API
- Roles API
- Users API
- UserRoles API
- ItemMetrics API
- ReviewerMapping API
- MonitoredEmployees API
- Evidence Of Review Async API
- Evidence of Review API
- Report Status API
- Supported OData query options
- Supported reporting endpoint API filters and their values
- Responses
- Managing Power BI templates for reporting APIs
- Configuring Microsoft Power BI Templates for Reporting APIs
- Accessing Veritas Surveillance reports and datasets through the OData web service
- Guidelines for using Veritas Surveillance templates with Microsoft Power BI Desktop
- TEMPLATE - Item Metrics
- TEMPLATE - Reviewer Mapping
- TEMPLATE- Evidence Of Review - Submit report request
- TEMPLATE- Evidence Of Review - View report data
- Saving, editing, and refreshing the Power BI reports
- Managing Audit Settings
- Working with Audit viewer
UserRoles - List by filters
GET https://<Reporting endpoint Base URL>/odata/userroles?Departments=[list of comma-separated values]&Scopes=[list of comma-separated values]&Users=[list of comma-separated values]
POST https://<Reporting endpoint Base URL>/odata/userroles
GET https://<Reporting endpoint Base URL>/odata/userroles?Departments=[23,25]&Scopes=[160,161]&Users=[3821, 55, 67]
Specify the following filters to obtain refined and selective results from this report.
Note:
Either Departments or Users is a mandatory parameter. The Scope is an optional parameter.
Name | Type | Description |
|---|---|---|
Departments | Mandatory (if the Users parameter is not provided) Optional (if the Users parameter is provided) | Specifies IDs of the departments to which users and their roles belongs to. : This API can pass a maximum of 100 Departments IDs as input. : JSON array of integers 'id'(identifier fields) that is Departments. |
Scopes | Optional | Specifies the scope of the users roles. Possible values are: 160 for application-level roles and 161 for department-level roles. : JSON array of integers 'id'(identifier fields) that is Scopes. |
Users | Mandatory (if the Departments parameter is not provided) Optional (if the Departments parameter is provided) | Specifies IDs of the users. This API can pass a maximum of 100 User IDs as input. : JSON array of integers 'id'(identifier fields) that is Users. |
To get the details of users and their assigned roles when only Users are mentioned, but Departments and Scopes are not specified.
To get the details of users and their assigned roles when only Departments are mentioned, but Users and Scopes are not specified.
To get the details of users and their assigned roles when only Departments and Scopes are mentioned, but Users are not specified.
To get the details of users and their assigned roles when only Users and Scopes are mentioned, but Departments are not specified.
To get the details of users and their assigned roles when Departments, Users, and Scopes are mentioned.
(For scenario 1 to 5) Status code: 200 OK
Invalid Input. An error occurs when only Scopes value is mentioned, but Departments and Users are not specified. Either the Departments or Users parameter must be provided as input.
POST https://<Reporting endpoint Base URL>/odata/Userroles
{
"Departments": [],
"Scopes" :[160]
"Users" :[]
}
Status code: 400 Bad Request Error Code: InvalidOdataQuery
See Supported OData query options.
See Responses.