Introduction

Kick-start your work by creating your Office document based on the latest and most up-to-date templates served to you in your favorite Office application on any device or platform.

Template Chooser for Office, Word
Template Chooser for Office, Excel
Template Chooser for Office, PowerPoint
Template Chooser for Teams
Template Chooser for SharePoint
Multiple Office App Awards Winner

Designed for Office 365

Supported Office Applications

The 'Template Chooser' runs within the following Office applications on Windows, Mac, iPad and Office Online:

Word
Word
Word
Excel
Word
PowerPoint
Word
Project
Word
Teams
Word
SharePoint
(coming soon)

Please note:  The 'Template Chooser' Apps might offer different features depending on the different Office applications on the various platforms.

Please note:  The 'Template Chooser for Office' in Project is only available on Windows.

Supported Storage Services

The  'Template Chooser' supports the following template storage locations:

Word
SharePoint Online
Word
Teams
Word
OneDrive

Please note: Teams and OneDrive can be deactivated on a tenant by tenant basis.

Supported User Accounts

The  «Template Chooser» supports the following user accounts:

Word
Office 365 Account
Word
Microsoft Personal Account

Variations

The  'Template Chooser' app will offer different features based on the account you are using or if you are a subscription user or not. If you are evaluating the app without a subscription you will not be able to configure all the options a paying user with a business subscription would be able to. If you sign in using a personal Microsoft account you will also not be able to configure any settings. Additionally, features available only to Office 365 Users like SharePoint Online will also be missing.

Personal

FREE

when using a personal Microsoft account.

Supported Libraries

OneDrive

Teams

SharePoint

Tenant Settings

Feature Settings

Custom feature settings like disabling OneDrive or removing the Yammer and Feedback form link.

Advertisement Free

New users will receive no e-mails from officeatwork.

Sample Libraries deactivated

Business

Evaluation

when using an Office 365 or Microsoft 365 account for evaluation purposes.

Supported Libraries

OneDrive for Business

Teams

SharePoint

Tenant Settings

Feature Settings

Custom feature settings like disabling OneDrive or removing the Yammer and Feedback form link.

Advertisement Free

New users will receive no e-mails from officeatwork.

Sample Libraries deactivated

Business

Subscription

when using a paid subscription with a Office 365 or Microsoft 365 account.

Supported Libraries

OneDrive for Business

Teams

SharePoint

Tenant Settings

Feature Settings

Custom feature settings like disabling OneDrive or removing the Yammer and Feedback form link.

Advertisement Free

New users will receive no e-mails from officeatwork.

Sample Libraries deactivated

Apps & Add-Ins

The following Apps and Add-Ins are included in the Template Chooser.

Onboarding Guide

This page will guide you through the steps required to deploy the 'Template Chooser' within your organization. The page is built in a check-list fashion and covers the most commonly used approach.

Please note:  Evaluation users are automatically captured in our marketing automation engine. To avoid that your users will be receiving marketing messages from us it is essential that you first activate the necessary subscriptions before making the add-in available to your users. You can also receive a trial license that will allow you to test all the features without your users being captured in our marketing automation engine. Apply for a trial here.

Prepare Infrastructure

Please make sure that the sub-domains cdn.officeatwork365.com and gateway.officeatwork365.com are trusted by all your browsers on all platforms and that your firewall/proxy is not interfering with those sub-domains. If your internal policies would allow it you can of course use *.officeatwork365.com instead of the individual sub-domains.

Configure Features

Use the Admin Center App to configure features like enabling or disabling OneDrive Libraries etc.

Prepare SharePoint

To enable SharePoint to be your storage location for your templates you need to first prepare SharePoint accordingly. The 'Template Chooser' requires a dedicated site collection called 'officeatwork' with some additional sub sites, lists and libraries within your Office 365 SharePoint tenant. For this we offer detailed documentation and a web application that does this for you.

Manage User Groups

As the deployment of all the Apps as well as the access to templates can be managed using «Azure AD» security groups we recommend creating/utilizing these groups accordingly. Please keep in mind that if done cleverly, new employees will automatically get access to the Apps and the templates simultaneously, just by adding a user into the appropriate security groups. We believe that this could simplify/automate your employee on-boarding process in regard to automatically getting access to your Office templates.

Access to the Template Chooser add-in

Access to the template libraries and files

Move your templates

Pre-consent Add-In access

Assign and promote the add-in to users

Verify your onboarding

Deployment

Aquisition

For Organizational use

All officeatwork Apps are made available via Microsoft AppSource. For deployments in organizations we recommend to use Office 365 Centralized Distribution available in the Office 365 Admin Center.

FOR Personal use

All officeatwork web apps are made available directly within the Office Application in Store experience offered in Word, Excel, PowerPoint, Teams and SharePoint. For Personal use we recommend installing the apps using the in Store experiences.

Office Add-Ins

Historically you might be used to deploy Office Add-Ins using MSI packages. This is not an option for our modern officeatwork cloud SaaS Office Apps/Add-Ins anymore as they are not build with the older (COM) platform dependent technology.

Please note: We do not offer any MSI package for our modern web based Apps and Add-Ins..

Centralized Deployment

The by far best way of deploying Add-ins for Office 365 is using the new 'Centralized Deployment' feature inside the Microsoft 365 admin center. This feature will allow you to deploy add-ins to your users on all devices and platforms. There are no local installations necessary for this to work. Check out the videos below to learn more about centralized deploying Web Office Add-Ins in Office 365.

What it is

3:12 Minutes

How it works

1:34 Minutes

Be sure to check if your tenant is ready for 'Centralized Deployment'. Here is a link to the Microsoft support document called 'Determine if Centralized Deployment of add-ins works for your organization' that will explain the requirements in detail. Microsoft also offers an Add-In (Word & Excel) that will perform automated checks to see if your infrastructure is ready for Centralized Deployment. It's called 'Compatibility Checker for Centralized Deployment'

Currently you can reach 'Centralized Deployment' by going to: Microsoft 365 admin center > Settings > Services & add-ins > Deploy Add-In

Please note: You must be an Office 365 admin to be able to sign into the Office 365 Admin portal. You will also need to use the ‘I want to add an Add-In from the Office Store‘ option as this will keep your add-ins up-to-date automatically!

Useful Resources

Sharepoinnt add-in catalog (for older Office versions)

Modern Web Office Add-ins can also be deployed for older Office version like Office 2013. For that you can use the SharePoint Add-In catalog deployment method. Please note that some features like showing icons in the ribbon in Office will not be available via this deployment path. This deployment method will though work for the officeatwork 365 Template Chooser and Content Chooser Add-Ins. Please expect limited functionality due to missing API's in Office 2013. Check out our 'Compatibility' page to learn more about any missing features for your Office version.

Useful Resources

Office

You can find our Add-Ins within the Office Store experience provide within the Office applications. Just us the 'Get it now' button to acquire and deploy the Add-In.

Appsource

You can find our Add-Ins for Office on AppSource. Just us the 'Get it now' button to acquire and deploy the Add-In.

Teams

Teams

You can find our Teams Apps within the Store experience provide in the Teams applications. Just us the 'Add' button to acquire and deploy any officeatwork Apps.

Appsource

You can find our Apps for Teams on AppSource. Just us the 'Get it now' button to acquire and deploy the app.

SharePoint

Installation details will be released once the 'Template Chooser for SharePoint' becomes available via AppSource.

Please note: If you see the 'Templates' button appear multiple times on your modern Document Library you might want to check the SharePoint 'Tenant Wide Extension' list for duplicates of the 'Template Chooser for SharePoint' app.

Compatibility

Check out the minimal Office versions required for running the officeatwork 365 Apps on your devices. Also see what specific features of the individual Apps are supported from what version onward.

Minimal Office Version

Minimal Office version required to run the officeatwork App.

Windows

Office 2013 (MSI)

15.0 (4855.1000)

Office 2016 (MSI)

16.0 (4390.1000)

Office 2019 (MSI)

all versions

Office 365 (C2R)

1602 (6741.0000)

iPad

Office 365

1.22

Mac OS

Office 365

15.20 (160315)

Office Online

Office 365

January 2017

Advanced document creation in Word

Creating new documents directly in Word using an optimized Word API especially designed for creating new documents.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

1612 (7668.1000)

iPad

Office 365

2.22

Mac OS

Office 365

15.32.0 (1703.0901)

Office Online

Office 365

March 2017

Advanced document creation in PowerPoint

Creating new documents directly in PowerPoint using an optimized PowerPoint API especially designed for creating new documents.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

in preview

iPad

Office 365

in preview

Mac OS

Office 365

in preview

Office Online

Office 365

January 2018

Advanced document creation in Excel

Creating new documents directly in Excel using an optimized Excel API especially designed for creating new documents.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

1808 (10730.20102)

iPad

Office 365

2.17

Mac OS

Office 365

16.17

Office Online

Office 365

September 2018

General App Features

Ribbon Icon

Access App via one or multiple icon in the Office ribbon.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

1603 (6769.0000)

iPad

Office 365

not applicable

Mac OS

Office 365

15.33.0 (1704.0900)

Office Online

Office 365

January 2016

Centralized Deployment

Deploying Word, Excel and PowerPoint Apps in Office.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

1704 (8067.2115)

iPad

Office 365

not applicable

Mac OS

Office 365

15.34.0 (1705.1500)

Office Online

Office 365

January 2016

Automatically open a task pane

Automatically load an App and open a task pane when opening a specific Word, Excel or PowerPoint document.

Windows

Office 2013 (MSI)

not available

Office 2016 (MSI)

not available

Office 2019 (MSI)

all versions

Office 365 (C2R)

16.0 (8121.1000)

iPad

Office 365

not applicable

Mac OS

Office 365

15.34.0 (1705.1500)

Office Online

Office 365

January 2016

Launching

In Office

Template Chooser Ribbon

Once the 'Template Chooser for Office' App has been assigned to you or you have acquired it via the Office Store/AppSource, it will automatically appear in the 'Home' tab of your Office application ribbon. To launch the App best click on the 'Templates' button. Be aware that the name of the Button 'Templates' can vary based on the Office language you are using. Please note that the icon for the 'Templates' button might vary depending on what Office application you are working in.

In Teams

Template Chooser Tab

Once the 'Template Chooser for Teams' App has been added to a channel of a Team it will be accessible as a channel Tab/App. To launch the App best click on the 'Templates' tab. Please note that the name of the 'Template Chooser for Teams' tab can vary as it can be renamed freely.

In SharePoint (coming soon)

Template Chooser Button

Once the 'Template Chooser for SharePoint' App has been added to a Site Collection in SharePoint it will be accessible as a button on any document library within that site collection. To launch the App best click on the 'Templates' button. Be aware that the name of the button 'Templates' can vary based on the browser language you are using. The Button will unfortunately not be available on Document Library Web Parts due to current SharePoint API limitations.

Signing in

Template Chooser Welcome Page

To get started with the 'Template Chooser' you need to connect it with your Office 365 work or school account or with your personal Microsoft Account. Click the 'Connect' (1) button to start the process. The actual sign in experience is provided by Microsoft.

Please note: You will not be able to sign in to the 'Template Chooser for Teams' or the 'Template Chooser for SharePoint' with an other user than the one you used for Teams or SharePoint. So if you want to switch the user in the 'Template Chooser for Teams' or the 'Template Chooser for SharePoint' you need to re-sign-in to Teams or SharePoint with that user.

Accounts

This App accepts Office 365 work or school account or personal Microsoft Account including GitHub accounts.

Consenting

The first time you connect the App you might be asked to consent to the permissions the App requires. Please go through those permissions carefully and grant consent as the App requires these permissions to function. If you do not grant consent the App will not work for you.

Navigation

'Libraries' button

Template Chooser navigation

The 'Libraries' button (1) will provide access to all of your content libraries. Use this button to switch between libraries.

'User' Button

The 'User' button (2) will provide links to resources such as:

Please note: Dependent on your application settings (you) made using the officeatwork Admin Center App, some items in the 'User' menu might have been de-activated and will therefor not be visible.

Template Chooser Setup SharePoint Online

To switch a library just click on the name of the existing library (1) at the top of the Add-In. That will bring up a list of all available libraries for you to choose form. You can then just click on one of the libraries to switch.

SharePoint Online Libraries

Setup

Automatic configuration

The officeatwork 'Template Chooser Setup App' is an Office 365 Web App designed to help you setup your SharePoint Online configuration for the officeatwork Template Chooser. The Web App will help you create a new SharePoint site collection named 'officeatwork' and a subsite named 'TemplateChooser'. Within that subsite it will also create a list named 'TemplateLibraries' and a document library named 'Templates'. The list and the document library will initially be populated with some sample data. If you prefer to do the setup work in your SharePoint online tenant work manually you can jump to the next section called 'MANUAL CONFIGURATION'.

Follow these steps to perform the configuration required to enable SharePoint template libraries within your Template Chooser Apps:

Please note: You need to be a SharePoint administrator AND an Office 365 administrator to run the 'Template Chooser Setup App'.

Please note: Please be aware that this initial setup process can take up-to 15 minutes to complete!

  • Start the automatic configuration by clicking the 'Template Chooser Setup App' button below:

    Template Chooser Setup App
  • Click on 'Sign-in as Admin'.
    Please remember that the account you use to sign-in must be an AAD account and the user must be an Office 365 AND SharePoint Admin.

    Content Chooser Setup
  • Click on the «Create Repository» Button.

  • Please be patient and wait for this process to complete — it can easily take up-to 15 minutes to complete.

  • After the repository is created return to the Template Chooser and re-load it.

  • You should now see at least one SharePoint template library in your list of template libraries.

Manual configuration

If you want to setup SharePoint Online without the «Template Chooser Setup App» for Office 365 you can configure SharePoint Online within your Office 365 tenant manually. It is important that the names for the site collection etc. are exactly as provided below. Follow these steps:

  • Create a new Site Collection named «officeatwork»

  • Create the subsite «TemplateChooser».

    Please note: Please be aware that the url must be exactly as written above and that upper and lower case matter (case sensitive)

  • Add a new list to this site collection named «TemplateLibraries»

  • Add the column of type «Hyperlink or Picture» with the name ‘Url’ (cases sensitive) to this list

  • Add a column of type «Choice» with the name ‘Applications’ (cases sensitive) to this list

  • Set the property ‘Type each choice on a separate line’ to
    Word
    Excel
    PowerPoint
    Project
    Teams
    SharePoint

  • Set the ‘Display choices using’ to ‘Checkboxes (allow multiple selections)’

  • Set the ‘Default value’ to ‘Calculated Value’ and enter the following formula in the input box
    =”;#Word;#Excel;#PowerPoint;#Project;#Teams;#SharePoint;#”

  • Leave all other properties at default settings

  • Add entries for each Document Library which contains templates by copying the URL of the document library into the «Url» field

  • Give each entry a name by typing a name into the Title field of each entry.

  • Define for each entry in what Office applications the library shall be visible. New entries will be visible in all Office applications by default.

  • Re-load the officeatwork 365 Template Chooser Web Office Add-in in your Office application.

Tip: Any document library within your SharePoint Online tenant can be used as a template library. There are no specific requirements other than that those listed libraries must be of type SharePoint document library.

Things that can go wrong…

SharePoint Online is quite complex and therefor things can be configured in a way that will not allow you to see your libraries.

No access to the Libraries List

No access to the Libraries List

When you get this message in the list of libraries it is most likely the case that you do not have access to the SharePoint list that holds the list of all SharePoint Document Libraries that should be shown as available libraries.

  • Click on the link ‘SharePoint Online libraries list’ in the message. This will try to open the SharePoint list using your Browser. If you have no access to the list, you should be seeing the default 'no access' message form SharePoint. Contact your SharePoint administrator to ask for access to that list.

SharePoint still not configured

In case you still see the initial configuration message after you have configured SharePoint online you might want to check if the users that encounter this have access to the root site collection of your SharePoint online tenant. If that is not the case users will see the original messages as shown below (1).

Template Chooser Setup SharePoint Online

Initially you need to consent to the App being allowed to use your SharePoint data. This consent can only be provided by an SharePoint online administrators.

Configuration

Template Chooser Setup SharePoint Online

At first you might have not configured your Office 365 SharePoint Tenant for the 'Template Chooser'. In this case, you will find a 'Learn more' link (1) below the 'SharePoint Online' library header. So if you want to configure your Office 365 Tenant’s 'SharePoint Online' to work with the 'Template Chooser' just click on the 'Learn More' link and follow the instructions presented on the web page.

Once your Office 365 Tenant’s 'SharePoint Online' has been configured for the 'Template Chooser' you will see a list of all available document libraries you have access to. The libraries are listed below the 'SharePoint Online' group header.

Manage Libraries

Template Chooser SharePoint Online Edit

If you want to manage the lists of 'SharePoint Online' libraries just click on the 'Edit' button (1) to the far right of the 'SharePoint Online' group header.

This will open a dedicated 'SharePoint Online List' in your Office 365 Share Point Online Tenant. The URL of the list will be something like this: https://[YourTenant].sharepoint.com/sites/officeatwork/TemplateChooser/Lists/TemplateLibraries.

Template Chooser SharePoint online Template Libraries

The actual adding and removing of libraries can be done using native 'SharePoint' functions. If you are not literate with 'SharePoint Online' we recommend you to go through the 'SharePoint' documentation or to reach out to someone with sufficient 'SharePoint' experience.

You need to create an item in this list for each 'SharePoint Online' Document library you want to use in the 'Template Chooser'. The 'Title' column will be used as the name of the library in the libraries list in your 'Template Chooser' Add-in. The 'URL' column must contain the URL of the library in your 'SharePoint Online' tenant you want to use. This could look something like this:
https://[YourTenant].sharepoint.com/sites/officeatwork/TemplateChooser/Templates. The Application column will allow you to determine in what Office application the library shall appear.

Tip: The libraries you use can be located in any site collection within your SharePoint root host of our Office 365 Tenant’s 'SharePoint Online'.

Tip: Use the rich security options provided by 'SharePoint Online' to determine what libraries are made available to users and groups within your organization.

Please note: The user will need at least read rights to the root site of the site collection you are connecting to.

Library names

By default the Title field in the SharePoint list will be used to display your library name in the product experience.

Attention: Your Title field label might be translated in your SharePoint experience! So, in for example a french SharePoint document library user experience the title column would appear as Titre and not Title. Nevertheless, the column labeled Titre will work :-)

Library Name Translation

If you are sharing your libraries across language regions you might want to translate the library names so that users can explore your libraries in their native language. To add translations to any library in you need to add an additional column to your SharePoint list (1 column per language). We offer a simple naming convention to enable this scenario:

Title + . + language code

So for instance, if you would want to show translated French library names you would need to create an additional column named 'Title.fr'. Make sure you spell the column correctly in your first attempt as renaming the column might only give it a different label but not actually rename the column Name/ID. We also recommend to create new columns via the SharePoint 'Library settings' page to make sure your column gets named correctly. Once you have created the column you can go ahead and add a translation for each library you wish to translate. Thereafter your users with a french user interface will automatically see the translated french library names.

Here is a link to a list of ISO 639-1 language codes you can use:
http://www.lingoes.net/en/translator/langcode.htm

Attention: make sure you type your language code in lower case - upper case will not work.

Attention: If your 'Title' field is translated in your SharePoint experience (for instance 'Titre' for french) you will still need to create your translation columns using the exact english spelling for your additional Title.LanguageCode columns.

Template name

Teams Libraries

Enabling / Disable

This feature is enabled by default. Licensed customers can disable this feature using the Admin Center App. Users signing in with a personal account or users using an evaluation license are not able to disable this feature.

Enable Teams

Initially you need to enable the Teams libraries feature. To do this you click on the enable (1) button. This will start an admin permissions flow that only Office 365 Administrators can complete.

Configuring

Manage Teams Libraries

At first you might have not configured your Teams libraries. In this case, you will find a «Manager Libraries» (1) button below the «Teams» library header. If you already have setup some libraries, you will not see the «Manager Libraries» button. In this case, you can use the «Pen» icon (2) to start managing your libraries.

Manage

Manage Teams Libraries

New Library

To create a new library just click on the «Add Library» (1) button. A fly-out appears, that will allow you to select a Team, a channel and if you wish any sub-folder within that channel. Navigate and select to the channel or folder you wish to use as a Template Library and click on «Create Library» button at the bottom of the list. With this you have created a new Template Library linked to the channel or folder you just selected. Be aware that you can only create one Template Chooser library per team. So once you have created a library for a specific Team that team will not show up anymore in the fly-out. Once you have created a Template library within a team that library will become visible for all your team members. There is no need for all team members to repeat this step of creating a teams library for any specific team.

Edit or Remove a Library

To edit an existing library just click onto the library entry (2) in the list of libraries. To remove the library just click on the «Remove» button at the bottom of the library properties. You can not rename a Teams library as it will always show the name of the Team as the library name. Use the arrow back at the top of the page to return to the libraries list.

Template name

Note: Teams uses SharePoint to store all files. So our officeatwork template libraries in Teams are actually native SharePoint document libraries. That is why the following explanation is talking about SharePoint document libraries.

OneDrive Libraries

Enable / Disable

This feature is enabled by default. Licensed customers can disable this feature using the Admin Center App. Users signing in with a personal account or users using an evaluation license are not able to disable this feature.

Configure

Manage OneDrive Libraries

At first you might have not configured your OneDrive or OneDrive for Business for the 'Template Chooser'. In this case, you will find a 'Manager Libraries' (1) button below the 'OneDrive' library header. If you already have setup some libraries, you will not see the 'Manager Libraries' button. In this case, you can use the 'Pen' icon (2) to start managing your libraries.

Please note: Organizational users that sign in with their Work or School account can choose to disable OneDrive support within the Template Chooser. This can make sense in case you want all your templates organized in SharePoint and not promote the management of templates on an individual level.

Manage

Manage OneDrive Libraries

New Library

To create a new library just click on the 'Add Library' (1) button. A fly-out appears, that will allow you to select a folder. Navigate and select to the folder you wish to use as a Template Library and click on 'Create Library' button at the bottom of the list. With this you have created a new Template Library linked to the folder you just selected.

Edit or Remove a Library

To edit an existing library just click onto the library entry (2) in the list of libraries. To remove the library just click on the 'Remove' button at the bottom of the library properties. To rename the library just click into the 'Name' field and change the name accordingly. Use the arrow back at the top of the page to return to the libraries list.

Samples Libraries

The 'Samples' libraries are here to help you to get a feeling of what the 'Template Chooser' can do for you without the need to setup your own libraries.
If you have not set up any of your own libraries the 'Template Chooser' will always select the first 'Samples' library for you by default when loading the libraries page.

Hide Samples Libraries

All sample libraries including the 'Samples' group will not be visible to organizational users with a Microsoft 365 or Office 365 Work or School account once you purchased a subscription and become a licensed user.

Templates

Creating new files based on a template

Creating NEw Files

Template Chooser Search

Once you have loaded a template library you can easily create a new document base on a specific template by clicking anywhere (1) on to one of the listed templates.

Please note: Dependent on your Office application and its version you might have to complete the download of the template via your browser. In that case follow the on-screen instructions and switch to your browser to download and open the template.

Searching Templates

Template Chooser Search

Use the search box (1) to search for contents with a specific name within the active template library.

Please note: Searching across multiple libraries is currently not supported.

Navigating Folders

Template Chooser Search

Use the ‘bread crumb’ navigation element (1) to move up your folder hierarchy. To navigate into a folder just click onto its icon.

Managing Templates

To manage your templates of the currently loaded library you just need to click on the 'View Online' (2) button. To manage templates from a different library you just need to switch to that library first before clicking on the 'View Online' button.

Supported file formats

Each Office application supports its specific file formats. See below what Office applications supports what formats.

Formats marked in bold are the recommended formats to use as they offer the best overall experience.

Word

Word
DOCX (1)
Word
DOCM (4)
Word
DOTX
Word
DOTM (4)

Excel

Word
XLSX
Word
XLSM (3)
Word
XLTX (2)
Word
XLTM (3)

PowerPoint

Word
PPTX (1)
Word
POTX (1, 2)

Project

Word
MPP
Word
MPT

Teams

Word
DOCX (1)
Word
DOCM (5)
Word
XLSX
Word
XLSM (5)
Word
PPTX (1)
Word
VSDM
Word
VSDX

SharePoint (coming soon)

Word
DOCX (1)
Word
DOCM (5)
Word
XLSX
Word
XLSM (5)
Word
PPTX (1)
Word
VSDM
Word
VSDX

(1) Support for inline preview in Template Chooser Add-In

(2) Due to some missing API's for the template file format in PowerPoint and Excel we recommend to use the document file format for templates to get the best user experience when creating new documents.

(3) Due to some missing API's for the macro file formats in PowerPoint across platforms these files are only supported on Windows and Mac.

(4) Due to some missing API's for the macro file formats in Word across platforms these files are only supported on Windows and Mac with a simple browser download experience.

(5) Please be aware that Office Online does not support macros. The file can be created and opened in Office Online but the macros will not be available.

settings

Top

The 'Settings' page will allow you to adjust the settings for this App. The page can be accessed via the 'User' menu.

Document

Template Chooser Settings

Open Add-in together witH this document

You might want the Add-In to automatically open alongside with a specific document. To do that you can use this 'Open Add-In together with this document' (1) setting.

Never

Choose this option if you do not want the Add-In to open together with your document (default setting).

Once

Choose this option if you want the Add-In to only open the next time you open your document, after that it shall not open automatically anymore. 

Always

Choose this option if you want to have the Add-In open together with your document all the time. Note that the Add-In will also open if you close your document with the Add-In closed and then re-open the document.

User

Template Chooser Settings

Languages

The Language dropdown (1) allows you to decide in which language the user interface should appear.

Automatic

The Automatic option will set your language setting to whatever your Office user interface language is set to. If no matching language is found the Add-In will default to English.

Specific Language

If the Language dropdown is set to a specific language, then that language will be used as user interface language for that Add-In.

Administrator

Template Chooser Settings

Admin Permissions

This option will allow an Administrator to grant permissions to the Add-In as Administrator. Learn more

To grant Admin Permissions just click on the «Grant Permissions» button (1) and follow the sign in and grant screens.

Security

We have built all our Apps with a solid and enterprise prove security architecture. We have chosen an architecture that follows these simple principles.

Sign-in / two factor authentication

As our Add-Ins connect to existing data providers, they automatically inherit the security settings defined by the specific data providers. In case of for instance Office 365, our Add-Ins will also support two factor authentication, if so defined within the customers Office 365 Tenant (Azure AD).

Office 365

So in the case of Office 365 the user will only see the data within the Add-In that the user has access to within Office 365. The data is always accessed in the scope of the user signed in to the officeatwork Add-In using the Office 365 user credentials.

Consenting

The first time the App wants/needs access to specific data in your Office 365 tenant, it needs to ask the user for the permission to do that. So if the App wants to read data from SharePoint online it will ask (for the first time only) the user if it is allowed to access the user's data in SharePoint online on the users behalf. The user can consent to this request for access. This consent experience is provided by the data source - in this case by Office 365.

If you are a larger organization you might find this annoying, that all users have to individually consent to the Add-In accessing the user's data for each data resource in Office 365. That is why we introduced an Admin Pre-Consent flow within all our Add-Ins. That will allow an Office 365 Admin to consent in the name of each user that the add-in might access the data of the individually signed in users. In some cases that flow will also open up access to data the user can not consent to as a user.

An Office 365 admin can grant the Template Chooser an admin consent allowing the Add-In to access all defined resources on behalf of each user without the Template Chooser having to asking the user for consent. Additionally, it will unblock the scenarios where the user can not provide consent, such as for example access to the user's lists and libraries in SharePoint online. Learn more about the access scopes supported by the template chooser on the dedicated Data Access page.

Why do Users provide consent?

Every time the Add-In wants/needs access to specific data in Office 365 for the first time it needs to ask the user for the permission to access that data. So for instance if the Add-In wants to read data from OneDrive it will have to ask the user if it is allowed to access the users data in OneDrive. The user can agree to this by providing a consent for accessing his or here data in OneDrive. This consent experience is provided by the data source - in this case by Office 365.

Why would administrators want to provide admin consent?

By providing an admin consent to the Template Chooser the admin can make all users within that Office 365 tenant more productive by saving each and every user having to individually consent for each resource separately. It will also reduce the questions users might ask in connection to dealing with the individual consent request they will face during their interaction with the Template Chooser.

What is the risk of doing this?

We can actually not identify any risk by providing an admin consent. In case you want to recall your admin consent, you can always use the Azure AD portal to revoke any consent.

Should all Administrators do this?

If you are a larger organization you might find this annoying, that all users have to individually consent to the Add-In accessing the users data for each data resource in Office 365. This has also an economical aspect as you can save the organization quite some time if you add the few minutes each users can save by having the resources they need pre-consented. So basically the larger your organization the more value doing an admin consent will bring. But we would reccomend to to this in all sizes of organizations as it just makes users more productive.

How do Administrators provide an admin consent?

Providing an admin consent is part of the settings options. Learn more about this on the settings documentation page. Learn more

As an Administrator I might not want to consent to all scopes?

In your organization you might not want to use all features of the Add-In, hence you will not want to provide consent for a data source you don't want to use. Unfortunately, the current Azure AD architecture for providing admin consent is restricted to one single consent flow, meaning that we as the developers of the Add-In can only offer one admin consent flow for all customers. This means, we need to put all the scopes into that one flow to allow every customer to use all the features they wish to use. The drawback is, of course, that some customers are forced to provide consent for instance for accessing 'OneDrive', even if they do not want to use (deactivated) this specific feature. We are actively working with Microsoft on being able to improve this scenario, allowing customers to admin consent to only those scopes they actually want to use and not being forced to consent to all as it stands today.

Data Scopes

Another hot security topic is what access permissions are being executed when user data or company data (IP) is being processed by the officeatwork Apps. Following our security principles our Apps do not have their own independent data access definitions. What the Apps can access is always governed by the data provider. In case of Office 365 this would be the data access schema provided by Office 365.

This data access is always scoped to the signed in user. It by any means does not enable an officeatwork employee to get access to your data. On the contrary, as we are using the same authentication infrastructure used by Office 365, your data is protected by the Office 365 security framework including multi-factor authentication. The actual App sign in screens are provided and hosted by Microsoft. You can see that as the officeatwork sign in process displays the identical sign in screens and flow as if you were to sign in to Office 365.

In other words, users can only access data within the Apps that they can access based on their existing access rights in Office 365. This also means that a user can not access data of an other user via the officeatwork Apps. It also means that the scopes below will not allow users to see more data than what they are allowed to see in Office 365.

So for instance the SharePoint 'Sites.Read.All' scope will only allow the user to see the SharePoint data that he or she has access too in SharePoint. It will NOT allow the user to see all data in all Sites in SharePoint as the data remains governed by SharePoint. So regardless what user interface the user is using, the screens provided by SharePoint or the screens provided by the officeatwork Add-Ins, the user will only get access to the data they have access to within SharePoint and as that access is governed by the Office 365 sign-in infrastructure, that data can not be access by other users then the ones that have access to your Office 365 tenant.

Sign-In

'Sign users in'

To be able to sign in the user the Template Chooser needs some permissions. This openid permission can be consented by the individual User.

The Template Chooser needs this permission to allow users to sign in to their organizational and/or Microsoft Account within the Template Chooser Add-In.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant openid

Check out the official documentation about his permission set here.

'Access your data anytime' respectively 'Access user's data anytime'

To be able to automatically sign in the user the Template Chooser needs some permissions. This offline_access permission can be consented by the individual User.

The Template Chooser needs this permission only to automatically re-sign-in the user when re-launching the Template Chooser. This saves the user from having to manually sign in to the Template Chooser on every launch of the Template Chooser. We do not use this permission other than to the user's convenience of automatically signing in the user.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant offline_access

Check out the official documentation about his permission set here.

Display Signed In User within the Add-In

'View users' basic profile'

To be able to show the users what account was used to sign in, the Template Chooser needs this permission to show basic profile information. This profile permission can be consented by the individual User.

The Template Chooser uses this permission to show the User data about the signed in users. That will help the user understand which account was used to sign in to the Template Chooser.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant profile

Check out the official documentation about this permission set here.

Evaluation support

'View users' email address'

To be able to access the users email address the Template Chooser need this permission. This email permission can be consented by the individual User.

officeatwork is using the first name, last name, and e-mail address during the evaluation phase of the Template Chooser so that we can connect, communicate and support the users evaluating the Template Chooser Add-In. We store the e-mail address in our marketing automation tool to be able to offer the best possible evaluation support to the users.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant email

Please note: User data of users using a paid officeatwork Add-In subscription will not be stored in our marketing automation tool. In this subscription case, absolutely no personal data of any user is recorded/stored on any officeatwork server or service.

Check out the official documentation about his permission set here.

Remember user settings

'Read and update your profile' respectively 'Read and write access to user profile'

To be able to store some user specific Add-In settings like the language the Template Chooser should present itself in, the Template Chooser needs the permission to store user settings information in the user's profile. This User.ReadWrite permission can be consented by the individual User.

The Template Chooser uses this permission solely to read and write Template Chooser specific user settings for the convenience of the user. This will, for instance, allow the Add-In to 'remember' the language setting the user has selected. So next time the user signs into the Add-In the language will be set correctly. All settings are stored in storage locations governed by the connected service like Office 365 or OneDrive etc.. officeatwork does not store user settings on any of their own servers or services.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant User.ReadWrite

Check out the official documentation about his permission set here.

OneDrive integration

'Have full access to all files you have access to' respectively 'Have full access to all files user can access'

To be able to find template files in the users OneDrive the Template Chooser needs this permission. This Files.ReadWrite.All permission can be consented by the individual User.

The Template Chooser uses this permission to load templates from OneDrive the user has access to.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant Files.ReadWrite.All

Check out the official documentation about his permission set here.

Teams integration

'Read and write all groups'*

To be able to tag a channel or a folder within a channel of a Team (Group) as a library the Template Chooser need some permissions. This Group.ReadWrite.All permission can only be consented by the Office 365 Admin.

The Template Chooser uses this permission to be able to tag a channel or folder of a team files list as a library among the teams the user has access to.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant Group.ReadWrite.All

Check out the official documentation about his permission set here.

'Read all users' full profiles'*

To be able to evaluate what Teams the user is member of the Template Chooser need some permissions. This User.Read.All permission can only be consented by the Office 365 Admin.

The Template Chooser uses this permission to be able to determine in what Teams the user is a member of.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant User.Read.All

Check out the official documentation about his permission set here.

SharePoint Online integration

Read items in all site collections*

To be able to find the template libraries and template files in SharePoint the user has access to the Template Chooser need some permissions. This Sites.Read.All* permission can only be consented by the Office 365 Admin.

The Template Chooser is using this permission to find and load templates from SharePoint Online the user has access to.

You can use the button to the right to trigger the consent flow for this particular scope.

Grant Sites.Read.All

Check out the official documentation about his permission set here.

Please note: We have been asked by many prospects and customers if we could not limit the data the Add-In can access within SharePoint Online. Unfortunately, this is currently the only scope available that will allow the Add-In to read the user's data in all the SharePoint Online sites, lists and libraries the user has access to. There is no scope available that would allow us to just ask for permission to specific sites, lists or libraries. This means that using the SharePoint feature will always request this scope allowing users to read and write to all sites they have already access to. We are actively looking into this with Microsoft in the hope to be able to better restrict the data the Add-In can access within the data already accessible to each specific user.

* requires admin consent

Visit https://portal.azure.com > 'Enterprise Application' to verify what permissions have already been granted for the Template Chooser App. This is also where you can revoke the permissions for the Template Chooser App.

Data Flow

One of the biggest security concern is how the data the Add-In processes flows and if the user's privacy and the companies IP is protected.

The following describes the main usage scenarios and how the data flows between the different actors like the user, the Add-Ins and other connected services.

Loading Add-In

When the Add-In gets loaded it uses encrypted communications via an high availability Azure CDN service. Loading the Add-In requires no User nor Customer Data.

Add-In loading data flow

Sign-In to Add-In

To sign in to the officeatwork Add-Ins you can use either your Microsoft personal or organizational account. The flow starts with the user signing in using Microsoft's sign in flow. After a successful identification by Microsoft a User Access Token is collected by a trusted officeatwork server side Azure function that then hands the Access Token to the Add-In combined with tenant settings data stored in an officeatwork controlled globally available Azure cosmos DB. This flow takes place without any connection to the customer's data.

Sign in data flow

Using Add-In

While the user is interacting with the Add-Ins data might be required. The access to that data is enabled via the User Access Token allowing the Add-In to read and write data in the name of the User directly without having to bypass any officeatwork server services.

Add-In usage data flow

Service Level agreement (SLA)

All officeatwork SaaS Apps are hosted across multiple data centers across multiple continents and regions on the Microsoft Azure platform. Please find below the services used with the links to the according Microsoft Service Level Agreement:

Roadmap

UNDER INVESTIGATION

Planned

In Development

Released October 2019

Released September 2019

released June 2019

released MARCH 2019

released January 2019

released November 2018

released August 2018

released JULY 2018

released april 2018

Released DECEMBER 2017

Released November 2017

Released October 2017

Released August 2017

Released April 2017

Released March 2017

Released December 2016

Released May 2016

Released March 2016