TABLE OF CONTENTS

• VSTO add-ins architecture
• Location by default for the files saved on the local machine
• Exchanges with the Power-user server

VSTO add-ins architecture

As a VSTO add-in for Microsoft Office, Power-user interacts with Microsoft Office according to the below basic architecture:

You can read more about the VSTO add-ins directly from the Microsoft website here.

Location by default for the files saved on the local machine

By default, the files mentioned on the above illustration will be located here:

• Registry files (including deployment manifest) are in HKEY_CURRENT_USER/SOFTWARE/Microsoft/Office/PowerPoint/Addins/PowerUser  (and the same for Excel and Word)
• The Application manifest and installation files are in C:\Users\<UserName>\AppData\Local\Power-user, although IT admins can also install them somewhere else

Additionnally, Power-user will save some additionnal files:

• Session logs and other temporary files are saved by default in C:\Users\<UserName>\AppData\Local\Temp\Power-user. The logs are overwritten every time the application is launched
• Content files that the users will browse from the application, such as templates, icons, maps, etc. are saved by default in C:\Users\<UserName>\Documents\Power-user 

Exchanges with the Power-user server

There are also several interactions with server :

• Most importantly, it needs to be reminded that no information about the files that the users are working on gets collected, by design and as per our Data Privacy Agreement. 
• Some data is still collected for license management, support and billing. Please see below some details:

• Such data is needed and used only for the below purposes :

• Finally, your admin of Power-user licenses can integrate corporate resources, and in particular PowerPoint presentations or Excel spreadsheets in the Library for the benefit of the users. By default, Power-user doesn’t need access to such files in order to integrate them, and Power-user will only know the link and name of the files. The files will be pulled locally from the given link on your system where they are stored, as illustrated below: