How it works

UpSlide library system is designed to access shared content directly from inside Office with no or minimal IT work required.

Global view


All shared Office content is stored in network folders and is replicated for each user in a local cache. Each time content is added or removed, a synchronization system makes sure that the local cache gets updated. UpSlide then displays the content of this local cache to the user.

If the user has an administrator license, he can also publish new content on the shared folders.

Network folders

UpSlide library system supports multiple locations for its content. Each of these folders called library location can be located on different servers and have a different set of access permissions.

This can be very useful in multiple architectures. For example, to access both a central corporate library and a decentralized country library.

Each of the library location contains .UpLib files organized in subfolders. An .UpLib file is simply a archive grouping the Office file, which contains the shared content, and the previews displayed within the library pane.

Local cache

UpSlide automatically synchronizes the library locations with a local cache. This has two main benefits:

  1. changes made by administrators are immediately visible,
  2. the library can be used off-line.

The synchronization system is started each time the library pane is opened in UpSlide and will react almost instantly to any edition of the library location (folder/file add/edit/delete).

The default location of the local Cache (%appdata%\UpSlide\Content\LibraryCache) can be customized.


UpSlide administrators, provided they have the required permissions (cf. below), can publish new content in the library and edit existing one.


UpSlide uses the user active directory read permissions on the library locations to filter accessible content. For example, the user below has access to the Share, Legal and Accounting locations. 

Removing his access to the legal part of the library would be as simple has revoking his access to the library location.

Similarly, to publish or edit content, an administrator must have write permissions on the targeted folder.


Technical limitations

We conducted tests to check for any technical limitations with our synchronization system. It appears that with 5000 users watching the same library location, the additional workload on the file server is barely noticeable.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk