Vitrium FAQs
Supported Browsers
| Desktop | Mobile/Tablet |
|
Chrome |
Safari Mobile |
* Excludes Firefox on iOS mobile devices (iPhones and iPads)
Supported PDF Viewing Apps
| Desktop (Windows) | Desktop (Mac) |
|
Adobe Acrobat Reader DC |
Adobe Acrobat Reader DC |
*Important Note: There is one minor known limitation, which is the “obscure page” (the page that shows the message “This page is protected”) sometimes does not appear in Bluebeam. This is a relatively minor limitation as it would only affect non-authenticated users. The message would still appear for all users in their browser and in their File Explorer or Finder preview panel.
In the Reports Tab, you can export the User Activity Log to CSV file and get a more detailed report on the user’s activity and session information. Below is a table that lists the columns included in the exported CSV file, along with a description of what data could appear in each column. At the bottom of this page is a listing of all the types of activity that can appear in the “Type” column.
Details in Exported report:
| Column Names | Description |
| ActivityDate | Date and time of the transaction in UTC time zone |
| IsSuccess |
Was the transaction successful? Did the user gain access to content, print, or login to the user portal successfully? (TRUE/FALSE) |
| Description | NOT USED and will be removed in time. |
| DocId | Internal record ID of the content. Unique value per content record. GUID format. |
| VersionId |
Internal record ID of the content version. Unique per version. If you subscribe to Vitrium Security Enterprise and use the Version feature, this will differ for each version uploaded. GUID format. |
| VersionName | This is a string that usually will have “Version: 1” and, if you subscribe to Vitrium Security Enterprise and use the Version feature, subsequent version uploads will increment that value by 1 each time, so “Version: 2”, “Version:3”, etc. During upload or using API calls, you’ll have the option of changing these values. |
| DocCode | Internal DocCode of the content. Unique for each content. |
| Filename (or ‘Content Title’ in column view) | Unless using APIs this will be the resulting PDF minus the “.pdf” file extension. Same for video, audio, images. The extensions are removed. The column “ContentType” will define the type of content. |
| DocTitle | NOT USED and will be removed in time. |
| SessionId | Only appears for VersionUnique Protected PDFs (a feature only available to Vitrium Security Enterprise customers). This will be the DocId of that PDF. |
| RemoteUnlockCode | Will contain the remote unlock code used to allow a remote PDF user to unlock a protected PDF. |
| ReaderId | Internal record ID of the User record. Unique value per content record. GUID format. If you are a Vitrium Security Enterprise customer that uses an External Service, this will be most likely be the users’ ID from your external system as you’re responsible for providing this value. |
| ReaderName | Username as seen in the User record. |
| GroupNames (or ‘Groups’ in column view) |
At the time this file was being exported, this lists any Groups that the user might belong to. This DOES NOT list Groups that the user might have been linked to at the time of the transaction! Nor does it have anything to do with DRM enforcement. |
| IpAddress | The IP that the user was linked to at the time of the transaction. |
| CountryCode | Using GeoIP database info, this is the ISO country code based on the IpAddress. For the USA and Canada IPs, this will also include the State and Province codes. |
| ComputerId (or ‘Tracking ID’ in column view) |
This code is how Vitrium manages device limits. For a Web Viewer, this is stored in the user’s cookie. For a Protected PDF, this is stored via Adobe or PDF-XChange. If users are in incognito or private browsing OR if they use ad blockers or other such browser extensions/add-ons that kill cookies, this can change each time they access content or log in. For the most part, this should be a static value for each type of browser that a user uses on a given device. This should also be static for Protected PDFs on a given computer where they use the same O/S user credentials to log in to that PC or MacBook. |
| ServerUrl | For Web Viewer, this logs the URL that initiated the transaction. For Protected PDFs, this is the server that Adobe pinged. |
| Message (or ‘Error’ in column view) | If there’s an error or denial to block the user from gaining access, the error code will be logged here. If you’re a Vitrium Security Enterprise customer with an External Service that provides custom error messages, this will also contain those messages. |
| ServerUrl | These are the endpoints that the Web Viewer or Protected PDF communicated with. |
| OfflineDays | Will contain the DRM policy offline days if there is one defined, for this transaction. |
| OfflineDaysDescription | Contains the string equivalent of OfflineDays. |
| WatermarkContent | Contains the watermark formula based on either the content setting or, if you’re a Vitrium Security Enterprise customer and using the VersionUnique API, it would list any overrides that you utilized. |
| IsIgnored |
If you cleared usage for this transaction, it will report TRUE. IsIgnored=TRUE records are no longer referenced when enforcing DRM policies and no longer count towards device limits. |
| AnalyticsSessionId | NOT USED and will be removed in time. |
| CustomField | NOT USED and will be removed in time. |
| Type (or ‘Method’ in the column view) |
Find details of the different types by opening this link in a new tab. or searching for What are the Activity Report “Method” codes in the FAQ section. |
| ClientAppName (or ‘App’ in column view) | Name of the browser or PDF viewing app that the user tried to access content with. |
| ClientAppVersion (or ‘Version’ in column view) |
Version of browser or PDF viewing app that the user accessed content from. |
| ClientLanguage | Language of the browser or PDF viewing app that the user accessed content from. |
| ClientOperatingSystem (or ‘OS’ in column view) | Name of the operating system that the user accessed content from. |
| ClientDeviceName | Type of device the user accessed content from. |
| ContentType |
Type of content (see FileName). Values will be: aud (audio), doc (PDF), img (image), and vid (video). |
Staff Users allow any Vitrium Master Administrator to add more staff users (and different roles) to their Vitrium Security account. They can control and limit what other staff can do or access.
IMPORTANT NOTE: The Staff Roles function is included with all Vitrium Enterprise accounts, or as an add-on for Vitrium Pro Lite and Vitrium Pro Plus accounts. Contact your Vitrium sales rep for more information on pricing. For more information on staff users click here.
Types of Staff Roles:
- Master Admin: has access to all tabs and features of the account, from uploading and managing content, to setting up Content Settings and DRM Policies.
- Support: has limited access to support-related tasks only such as viewing content, users, groups and reports, but no editing rights
- Permission Manager: has limited access to managing permissions only which include adding and editing users and groups, assigning them to content, and managing Content Settings, Watermarks and DRM Policy Settings
- Content Manager: has limited access to managing content only which includes uploading and replacing content, and managing Content Settings
- System Viewer: has limited access to viewing rights only, no editing rights
Here is a detailed checklist of what each type of role can do or has access to:
OVERVIEW OF VITRIUM SECURITY STAFF ROLES
| Master Admin | Support Role | Permission Manager | Content Manager | System Viewer | |
| Content / Folders | |||||
| View & Search Content | x | x | x | x | x |
| Edit Content | x | x | |||
| Activate / Deactivate / Delete Content | x | x | |||
| Assign Content Permissions | x | x | |||
| Ability to Decode Content | x | x | |||
| Users & Groups | |||||
| Add, Edit, Import & Export Users and Groups | x | x | |||
| View and Search Users & Groups | x | x | x | x | |
| Add or Remove Users to Groups | x | x | |||
| Activate, Deactivate, or Delete Users and Groups | x | x | |||
| Clear Use for User | x | x | x | ||
| Settings | |||||
| View All Settings & Edit My Profile | x | x | x | x | x |
| Add or Edit Support URL | x | ||||
| Add or Edit Time Zone and Date Format | x | ||||
| Add or Edit Content & Watermark Settings | x | ||||
| Add or Edit DRM Policy Settings | x | x | |||
| Add or Edit Web Viewer & Portal Settings | x | ||||
| Add or Edit Staff Users | x | ||||
| Add or Edit SSO Settings & External Services | x | ||||
| Add or Edit Security Settings | x | ||||
| Add or Edit SMTP Settings | x | ||||
| Dashboard / Reports | |||||
| View Dashboard & Reports | x | x | x | x | x |
| Export Reports | x | x | |||
| API / Integration | |||||
| Make API Calls | x |
Vitrium Security offers two types of secured outputs: (1) a secure web link and (2) a protected PDF file (for document conversions only). The concept of ‘saving a file’ is different for each type of output:
Secure Web Link
Although you can ‘save’ a web link by bookmarking it, you cannot download the content. The Vitrium customer can set a number of days of ‘offline access’ as part of the DRM policy setting but even if that is allowed, the user can click the ‘Save to browser’ button in the web viewer and the content gets saved in the browser’s cache or memory for offline viewing. Again, the content does not get downloaded anywhere.
Protected PDF File
Content and files that are protected with Vitrium Security are protected no matter where they reside or where they are saved – on a local computer, network drive, file sharing application, or a mobile device – the security travels with the protected PDF document. So theoretically, the user can save the file but if they save it to a public computer or shared network, the content itself cannot be viewed or accessed unless the person is authenticated. This is why Vitrium Security can be an ideal solution to combine with an existing content management or document management system.
When “Fillable PDF” forms are protected, after successfully unlocking the content, the user might need to enter data into the form(s) and save that entered data to a new file and send it back to someone. The new PDF is protected in the same way as the original PDF and the same DRM policy remains in effect.