Add watermarks when files are opened or downloaded in SharePoint Online / Office 365

Posted at: 17:45 on 17 December 2015 by Muhimbi

confidentialOne of the more popular features of the on-premise version of the Muhimbi PDF Converter for SharePoint is the ability to add watermarks – including meta-data, ip-address, date/time information and user information – the moment a file is downloaded or opened. The file as it is sits in SharePoint remains untouched, but the file that is downloaded to the user includes the watermarks. At the same time the PDF file can be secured and encrypted to make sure the watermarks cannot be touched. For details about how this works for the on-premise version – largely identical to the online product – see this blog post.

Brilliant feature, quite often used for security / DRM-light purposes, but up until now only available for SharePoint On-Premises as providing this functionality in SharePoint Online – which is a very restricted platform – has proven to be….well…..tricky.

Well, that ends today as we are happy to announce the general availability of this functionality for the PDF Converter for SharePoint Online. Read on for details about how it works and how to enable it.

Update September 2020: This functionality is no longer limited to just PDF files, it also works with MS-Word, Excel and PowerPoint documents. For details see this blog post.

 

How it works

Before we go into further detail, let’s agree on a short name for this Feature as ‘Real Time Watermarking & Security when a file is accessed’ doesn’t roll off the tongue. Internally our team calls it ‘OnOpen’ as in something happens when a file is opened. So OnOpen it is, at least for the remainder of this post.

Once OnOpen is enabled (see the end of this post for details), whenever a PDF file is downloaded our software automatically adds any configured watermarks and security settings while the file is being sent to the user. It is up to the Site Administrators and List Owners to define these settings.

When OnOpen is first enabled on a site collection the settings are restricted by default. Site Collection Administrators will need to navigate to Site Settings / PDF Watermarking Settings (and/or PDF Security Settings) to specify the default settings and optionally specify if List Owners can override these settings.

 

WM-OnOpen-SiteSettings 
PDF Watermarking settings screen as opened from Site Settings.

 
Please note that by simply specifying this information at the Site Settings level, watermarks are NOT automatically enabled in the Site Collection’s Lists and Libraries. Although the default settings can be inherited from the Site Settings, it must be enabled on each Library or List manually and individually.

If there is no need to centrally control the content of the watermark and security settings then make sure the Allow overriding option is enabled. This makes it possible for the details to be specified manually on each list or library.

To either manually specify the settings at the List or Library level, or activate the centrally specified settings, navigate to the relevant list or library, and from the List / Library ribbon tab select Library Settings / List Settings. This screen contains two new entries,  PDF Watermarking Settings and PDF Security Settings, clicking the former shows the following screen.
 

WM-OnOpen-LibSettings 
PDF Watermarking settings screen as opened from Library Settings

 

This screen provides the option to inherit the centrally specified settings, or – if permitted – manually specify settings and an optional filter.

By default watermarks are applied for every PDF file that is opened, but by specifying a filter it is possible to narrow it down based on a file’s meta-data, which can be very powerful. E.g. apply a ‘DRAFT’ watermark when the document status is set as such and skip the watermark if the status is ‘Final’.

Although adding static watermarks that don’t change over time can be very useful, the same can be achieved using our workflow facilities that only apply the watermark once rather than every time the document is opened. The real power of the OnOpen facility comes from the ability to insert Meta-Data or Macros in a watermark. This allows such scenarios as:

  • Apply a watermark showing when the document was opened from SharePoint.
       Opened on '{LONG_DATE} / {LONG_TIME}' 
     
  • Include the name, login id and ip-number of the user who downloaded the document, a great security feature if a document shows up in a place it is not supposed to show up.
      Opened by '{LOGON_USER}' ({USER_NAME}) on '{LONG_DATE} / {LONG_TIME}' from IP '{REMOTE_ADDR}'
     
  • Include the Title, file name and last modified date in a document.
      Title: {Title}, File: {FileLeafRef}, Modified: {Modified}
     
  • Add hidden watermarks to a document. E.g. fully transparent text that is invisible to the user, but can be extracted at a later date in case a document is leaked or shared with an unauthorised party.
     
  • A mix of any of the above or any of the other meta-data fields and macros. A full list of Field codes and Macros can be found in this Knowledge Base article.

 

Finally, it is not just about watermarking as anyone with basic ‘Google search’ skills can download a simple PDF editor. To prevent users from modifying watermarks, and add additional layers of security by locking down printing and content copying, a Secure OnOpen facility is available as well.
 

Secure-OnOpen-ListSettingsApply Security when a file is opened

  
The concept is the same. Defaults can be specified at the Site Collection level, individual settings can then be enabled at the List or Library levels. Separate filters can be specified if needed. The available security settings are as follows:

  • Open Password: The user accessing the PDF file must know a specific password to open it.
  • Owner password: No password is needed to view the content, but all content is encrypted and any specified security options are locked down.
  • Security Options: Specify which option to lock down. The most popular ones are ‘Disable Printing’ and ‘Disable Content Copying’.

 

What happens when a document cannot be processed?

Although this facility is built upon an established and resilient platform, there are situations where a document cannot be processed. For example if the PDF is corrupt, already encrypted or the subscription has run out of monthly operations. It is important to decide up-front what to do in cases like this.

WM-Realtime-Settings

How the system deals with problematic situations can be configured using the PDF real-time settings link under Site Settings. The options are as follows:

  1. Show the original, unprocessed, document: For situations where watermarking or PDF security is a nice-to-have, but no show-stopper, you may want to choose this option, which will return the original document as if the OnOpen facility is not active at all.
  2. Block access to the original document: This option, which is the default, blocks access to the document if it cannot be processed. This is generally used in situations where the document MUST be processed before it is sent out, no exceptions.

 

 
How to enable

So, all in all a pretty cool feature, however it must be enabled by a Site Collection Administrator before it can be used. For details about how to do this see this Knowledge Base Article. Don’t forget to enable the Automatic PDF Processing App Feature after elevating the privileges, both steps are described in detail in the article.

Please note that extra installation steps are required when using this functionality in a List or Library utilising the Modern Experience. Details can be found in this Knowledge Base article.

 

Any questions or feedback? Have a look at the FAQ, leave a comment below or contact our friendly support desk.

.

Labels: , , , ,

PDF Converter API and Server Platform 8.0 - New InfoPath Converter & QR Code Watermarks

Posted at: 16:45 on 09 December 2015 by Muhimbi

PDFConverterServicesBox4_thumb3

We are happy to announce the new 8.0 release of the Muhimbi PDF Converter API and Server Platform (New releases for the PDF Converter for SharePoint and PDF Converter for SharePoint Online are available as well) 

The number of new features and changes are considerable and include a completely overhauled InfoPath converter, a new setup experience, Support for SharePoint Online / Office 365 and much much more. 

The following blog posts provide more detail:

A quick introduction for those not familiar with the product: The Muhimbi PDF Converter API and Server Platform is an ‘on premises’ server based SDK that allows software developers to convert typical Office files to PDF format using a robust, scalable but friendly Web Services interface from Java, .NET, Ruby & PHP based solutions. It supports a large number of file types including MS-Office and ODF file formats as well as HTML, MSG (email), EML, AutoCAD and Image based files and is used by some of the largest organisations in the world for mission critical document conversions. In addition to converting documents the product ships with a sophisticated watermarking engine, PDF Splitting and Merging facilities, an OCR facility and the ability to secure PDF files. A separate SharePoint specific version is available as well.

  Before--After_thumb3New InfoPath converter on the right (old on the left), no more rendering inconsistencies.


In addition to the changes listed above, some of the main changes and additions in the new version are as follows:

1715 Excel New Strip DIPs from Excel files to reduce problem during conversion.
2519 HTML Fix Hang when converting HTML to PDF.
2376 InfoPath Fix Non-negative number required when converting InfoPath forms on some systems.
1207 InfoPath Improvement Improve quality of Images embedded in InfoPath forms.
1829 InfoPath Improvement InfoPath conversions have grey border.
1495 InfoPath Improvement InfoPath Conversion – Externally referenced images don't always finish loading.
668 InfoPath Improvement InfoPath Conversion - Character spacing is inconsistent.
2349 InfoPath Improvement InfoPath Temp file names need to be made more unique.
2499 Merging Fix Pages are repeated when merging certain documents.
2350 Merging Fix PDF Attachment not recognised in some cases.
2332 Merging Fix Error generating TOC for PDF file that has internal attachments.
1824 Merging New Feature Request - Force new documents to start on odd pages during a merge.
1950 MSG Fix MSG - Some formatting is incorrect when HTML email contains inline images.
1951 MSG Fix MSG - Converter does not handle RTF containing binary data.
2504 MSG Fix MSG - Compressed-RTF data size mismatch.
2372 MSG Fix MSG - Email text alignment has changed between product released
2333 MSG Fix MSG - System.ArgumentOutOfRangeException: Index and count must refer to a location within the string.
2195 MSG Fix EML - Email converted with 7.2 does not look as good as in 7.0.
1962 MSG Improvement MSG - Conversion of Office shapes.
1949 MSG Improvement EML - Improve handling of RTF content in EML messages.
2539 MSG Improvement MSG - Incorrect Sent Date in some edge cases.
2358 MSG Improvement MSG - Display text when sent date is empty.
2271 MSG Improvement MSG – Bookmark names of converted email / attachments don’t match Outlook.
2537 OCR Fix PDF Syntax errors after carrying out OCR on some documents.
2498 OCR Fix OCR using German Locale - Input string not in a correct format.
2373 OCR Fix Some files are not OCRed at all.
2346 OCR Fix OCR Not carried out properly on certain complex files.
2180 OCR Fix OCR text action throws exception 'There were no results returned.'
2020 OCR Improvement JPEG2000 encoded PDFs not supported by OCR.
2181 OCR Improvement OCR Text activity - return meaningful error message if license validation fails.
2360 Other Fix System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
2316 Other Fix Deadlock while saving watermarked files in parallel.
2317 Other Fix Collection was modified; enumeration operation may not execute in Save method under load.
2318 Other Fix Object reference not set to an instance of an object. FontDictionaryBeginSave in Save method under load
2319 Other Fix System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. in PdfTrueTypeFont.CreateFontInternal method under load.
2320 Other Fix Object reference not set to an instance of an object in PdfCacheCollection. GetGroup under load
2298 Other Fix PdfUriAnnotation disappears.
2033 Other New Carry out default printer check during each conversion.
1380 Postscript New Add support for converting .PS & .EPS files
1813 Setup Improvement Service installer does not run on systems with only .net 4.5 installed.
2134 Setup Improvement Deployment issues on certain Win2K12R2 systems.
2040 Setup New Detect Machine Name of Conversion Server and automatically change config file.
2028 Setup New Carry out Office Activation Check.
2029 Setup New Check for Office User Profiles for Conversion Service Account.
2031 Setup New Add .Net v3.5 Runtime Availability Check.
2035 Setup New Automatically deploy license file during installation.
2036 Setup New Carry out Firewall Check and open appropriate port.
2021 Setup New Check user privileges during installation.
2024 Setup New Carry out Office version check during installation.
2104 Setup New Digitally sign installer
2157 Watermarking Fix Ellipse watermark action - incorrect PageOrientation value.
2301 Watermarking New Add support for QR Code watermarking.

 

For more information check out the following resources:


As always, feel free to contact us using Twitter, our Blog, regular email or subscribe to our newsletter.

Download your free trial here (50MB). .

.

Labels: , , ,

Subscribe to News feed