The Weagree Wizard’s SharePoint integration allows the user to seamlessly store any contract or entity-related file, generated in Weagree or manually uploaded, on SharePoint. SharePoint sites, folders and dynamic paths can be selected or configured to determine where any file will be stored by default (dependent first and foremost of the user’s access rights within SharePoint itself and with the option to provide certain users more freedom in choosing a precise storage location). Any such file can  then be retrieved or even directly edited again from within the Weagree Wizard at any time, as if it were stored in Weagree itself.

SharePoint integration can be enabled and configured as follows:


1. Go to and click on New registration.

2. The page Register an application will load. Here, you must:

a. enter a descriptive name
b. under Supported account types, select Accounts in this organizational directory only ([your default directory] only – Single tenant)
c. under Redirect URI (optional), select Web as platform and insert the applicable address: https://[portal name]
d. click Register

3. The Overview of the new app will load. In the menu on the left, click Authentication.

4. Under Implicit grant and hybrid flows, select both Access tokens (used for implicit flows) and ID tokens (used for implicit and hybrid flows).

5. Click Save.

6. In the menu on the left, click Certificates & secrets.

7. Click New client secret.

8. The Add a client secret panel will open. Enter a fitting description, select a duration and click Add. A new client secret will appear on the page, with an expiration date, a Value and a Secret ID.

9. In the menu on the left, click API permissions.

10. Click Add a permission.

11. The Request API permissions panel will open. Here you must:

a. click Microsoft Graph
b. click Delegated permissions and then tick the following permissions (you can use the search bar to quickly find them):

    • Directory.AccessAsUser.All
    • Directory.Read.All
    • Directory.ReadWrite.All
    • email
    • Files.Read
    • Files.Read.All
    • Files.ReadWrite.All
    • Mail.ReadWrite
    • Mail.Send
    • offline_access
    • openid
    • profile
    • Sites.Read.All
    • Sites.ReadWrite.All
    • User.Read

c. click Application permissions and then tick Sites.Selected
d. click Add permissions

12. On the API permissions page, click Grant admin consent for [your default directory].



1. Open the Administrator page (click on the cog icon in the top-right corner, next to the logout link).

2. In the menu on the left, click Configuration Weagree Wizard and then Login & user authentication.

3. In the bottom-right, enable External authentication if it is not active yet.

4. In the bottom-right, click Microsoft. The pop-up Edit login provider will open. Here, you must:

a. enable Active
b. in the Application (client) ID field of the pop-up, insert the string of characters next Application (client) ID on the Overview page of the Azure app, as mentioned above
c. in the Client secret field of the pop-up, insert the string of characters under Value on the Certificates & secrets > Client secrets page of the Azure app, as mentioned above
d. in the Directory (tenant) ID field of the pop-up, insert the string of characters next to Directory (tenant) ID on the Overview page of the Azure app, as mentioned above (note: you may need to save your previous settings and reopen the pop-up for this field to become visible)
e. enable Use for login
f. click Save

5. In the menu on the left, click API integrations.

6. Click SharePoint.

7. On the subtab SharePoint that appears on the right, switch on the Active button.

8. On the subtab File storage that appears below it, switch on the Active button.

9. Click the magnifier icon for each SharePoint site field to select the applicable SharePoint site.

10. Insert a format for the default (Catch-all fallback) folder structure. Note the following:

a. If left blank, files will be stored in the root of the SharePoint site.
b. You can click the magnifier icon next to the Folder structure field to add variables like the contract description or a party name.

Example: Contracts/[relation.2.shortName] will store files on the designated SharePoint site, within the Contracts folder and in subfolders matching the short names for the counterparties.

11. Optionally, insert formats for the default (general, contract or file) folder structures for contract entries, projects or the entity management.

12. Click Save.