InstanceID: using multiple simultaneous instances in GroupDocs.Viewer for .NET
Two months ago we presented a new feature called InstanceID in GroupDocs.Viewer for .NET for the first time. In short, InstanceID allows you to configure several simultaneous instances of GroupDocs.Viewer associated with different independent root storage paths. Since that time, we’ve received a lot of feedback on the feature and this time would like to clarify how you can benefit from InstqanceID and how to configure it correctly in more details. Those of you who are familiar with GroupDocs.Viewer for .NET probably already know that in order to configure the viewer, a root storage path must be specified via the Groupdocs.Web.UI.Viewer.SetRootStoragePath method. The files you want to display to end users must be placed within the root storage path or its subfolders. All temporary files along with log files are also stored in dedicated subfolders within the root storage folder. Now, there is a File Explorer option available for end users via the viewer’s widget. When enabled, this option allows users to browse through the local file storage, select documents and view them using the viewer. The file storage can be the root storage folder and its subfolders. In other words, when the File Explorer option is enabled, end users can potentially browse through the entire root storage folder and access all files, including temporary and log files, via the viewer. And here is where the problem arises. There may be cases when end users need to be able to browse through and select documents on their own, but their access rights must be restricted to a specific folder. Or, for example, there may be several different user groups each having access to different files storages. This is where InstanceID can be of great help. It allows you to configure multiple simultaneous root storage folders, absolutely independent one from another, and then assign them to different users or user groups. Recently we’ve prepared a detailed guide on how to configure and use InstanceID properly and are welcoming everyone who is interested in this feature to read it here.