This article aims to present the technical and security prerequisites for
installing, updating, and using the Jint solution, as well as the installation procedure.

The installation steps must be followed by a person who is an Entra ID administrator and
global administrator.

Table of Contents

1. Introduction
   • 1.1 Architecture of the Jint Solution
   • 1.2 Deployment of Packages
2. List of Prerequisites
   • 2.1.1 At the SharePoint Level
   • 2.1.2 At the Entra ID Level
   • 2.1.3 At the Network Security Level
   • 2.2 Deployment of SharePoint Packages
   • 2.3 Approval of Microsoft API Calls
3. Installation Steps
   • 3.1 Preparation of the SharePoint Tenant
   • 3.2 Approval of Applications (Configurator and Jint APIs)
   • 3.3 Granting Permissions to the App Catalog
   • 3.4 Communication of Information to Jint
   • 3.5 Deployment of the Solution by Jint
   • 3.6 Approval of Microsoft API Permissions
   • 3.7 Approval of Jint API Permissions
   • 3.8 Authorization of Jint Service Addresses
4. Using the Jint Solution

1. Introduction

1.1 Architecture of the Jint Solution

The Jint solution consists of:

• A set of SharePoint packages,
• A back-office management tool, called the Jint Configurator throughout this document,
  in the form of a web application whose authentication relies on your Microsoft account,
• A set of APIs whose authentication also relies on your Microsoft account.

1.2 Deployment of Packages

Jint extends the functionalities of Microsoft SharePoint. To do so, we deploy
packages in your SharePoint environment. These deployments occur automatically
each time we publish a new version of them.

2. List of Prerequisites

2.1 Summary

Here is a summary of the prerequisites for each component. They are detailed in the following sections.

2.1.1 At the SharePoint Level

• Administrator access to the app catalog:
  • Approval of an Entra ID application, Jint Deployment, requesting the
    application permission Sites.Selected.
• Approval of the necessary Microsoft API permissions
• Approval of the necessary Jint API permissions

2.1.2 At the Entra ID Level

• Approval of 5 Entra ID applications:
  • Jint Deployment
  • Jint Configurator
  • Jint Administration
  • Jint Site Engine
  • Jint Contribution Center

2.1.3 At Your Network Security Level

Add the addresses of the Jint services to your list of authorized addresses.

2.2 Deployment of SharePoint Packages

To deploy the SharePoint packages, our deployment automation requires administrator rights
on the app catalog, as Microsoft does not offer finer-grained rights. These rights must be granted to our Entra ID application, Jint Deployment.

2.3 Approval of Microsoft API Calls

Furthermore, to function correctly, our components call Microsoft APIs on behalf of the user.
For this, a set of Microsoft API call permissions must be approved on your SharePoint tenant:

• Calendars.Read

• Calendars.ReadWrite

• Group.Read.All

• ChannelMessage.Send

• Mail.Read

• Sites.Read.All

• User.Read.All

• User.ReadBasic.All

• Tasks.ReadWrite

• Team.ReadBasic.All

• Access_as_user

If these permissions have not already been approved, they must be approved once the Jint packages are deployed.

3. Installation Steps

Once the above prerequisites have been validated, the installation steps are as follows:

1. Preparation of SharePoint sites,
   Performed by the Client’s Global Administrator
2. Approval of applications necessary for Jint to function properly,
   Performed by the Client’s Entra ID Administrator and Global Administrator
3. Communication of the information necessary for installation to Jint,
   Performed by the Client or Integrator
4. Deployment of the solution by Jint,
   Performed by Jint
5. Approval of Microsoft API calls.
   Performed by the Client’s Global Administrator and Entra ID Administrator
6. Authorization of Jint service addresses
   Performed by the Client’s Network Administrator

Except for step 4, these steps must be performed by the Client. At the end of these steps, the
Jint solution is usable by the Client and their Integrator.

 

3.1 Preparation of the SharePoint Tenant

Access level required for this step: Global Administrator.

Preparing your SharePoint tenant consists of ensuring the creation of the global app catalog. Using a global administrator account, access the Microsoft 365 admin console: https://admin.microsoft.com.


In the left menu, select “Show all” then click on “SharePoint” under the “Admin centers” section:




In the “More features” menu of the SharePoint admin center, click the “Open” button in the “Apps” section:

 

The app catalog is created if it did not exist.


For each site in the subscribed scope, you will need to create the corresponding app catalog. This is done via some PowerShell commands with an account that is both a global administrator and an administrator of each target site:





# Install the Microsoft.Online.SharePoint.PowerShell module Install-Module -Name Microsoft.Online.SharePoint.PowerShell
# Connect to the SharePoint tenant
Connect-SPOService -Url https://<your-tenant>-admin.sharepoint.com
# Create/activate the app catalog for each site collection
Add-SPOSiteCollectionAppCatalog -Site https://<your-tenant>.sharepoint.com/sites/<site-name>

3.2 Approval of Applications for the Configurator and Jint APIs

Access level required for this step: Entra ID Administrator.

To authorize the Configurator and our APIs to authenticate your collaborators, you must approve
the following applications by clicking on the corresponding links:

Here is the description of each application:

• Jint Deployment is the application that performs installations and updates
  of the Jint solution on your Tenant. You will grant it administrator rights
  on the app catalog to deploy the SharePoint packages.

• Jint Configurator is the Jint back-office. It allows you
  to administer the solution. It requests delegated permissions to identify
  the user accessing the Configurator and configure Microsoft audiences:

  • User.Read

  • GroupMember.Read.All

• Jint Administration enables the activation of the “Unified Experience” features.
  It requests the following delegated permissions:

  • User.Read

  • SharePoint AllSites.FullControl

• Jint Site Engine offers duplication and creation of fully populated sharing spaces
  from a template. It requests delegated permissions:

  • User.Read

  •  SharePoint AllSites.FullControl

  • SharePoint TermStores.Read.All

• Jint Contribution Center allows you to create and share your content more simply and efficiently

  • User.Read

  •  SharePoint AllSites.FullControl

Delegated permissions are permissions allowing an application to access certain
Microsoft 365 domains on behalf of a user. They enable Jint to display
all relevant information for each user. More information on delegated permissions
can be found here.

3.3 Granting Permissions to the App Catalog

Granting permissions to our Entra ID application is done solely via a set
of calls to the Microsoft Graph API.

We offer you a downloadable PowerShell script here to make these calls easier.

This script will grant administrator rights to our Jint Deployment application on your app catalog.

 
During execution, depending on your PC configuration, you will be prompted to accept downloading and installing modules from the internet: Microsoft.Graph.Sites.

You will also need an account that is an Entra ID administrator to authorize the script to interact with your Microsoft 365 environment via the delegated permission Sites.FullControl.All, and a global administrator to grant the correct permission to our application.

Once the archive is downloaded, extract the script to the folder of your choice. Then, for each site collection in scope, right-click the file and select “Run with PowerShell.” The script will then ask you to provide the URL of the app catalog site.

Are you encountering an error while running the PowerShell script?
Check our documentation on this topic: PowerShell Script – Troubleshooting Execution Errors During Installation

3.4 Communication of Information Necessary for Installation to Jint

Access level required for this step: Entra ID Administrator

To proceed with the installation of Jint, we need the following information:

• Information about your Entra ID/SharePoint tenant:
  • Entra ID tenant ID,
  • Initial name of the Entra ID/SharePoint tenant,
• URL of the app catalog site identified in section 3.2,
• List of identifiers of the Jint solution managers.

Once this information is collected, it must be communicated to your Jint contact.

The following chapters detail where to find some of this information.

3.4.1 Information About Your Entra ID Tenant

Access the overview section of the Entra ID portal. The tenant ID is named “Client ID” in the interface:

For the initial tenant name, go to the “Custom domain names” menu and look
for the entry ending with “.onmicrosoft.com”. You can use the filter bar. The initial name of
your tenant is what precedes “.onmicrosoft.com,” “Jint” in the example below.

3.5 Deployment of the Solution by Jint

During this step, the Jint teams proceed with the initial deployment of the SharePoint packages,
as well as the initialization of your access to the Jint Configurator.

Once completed, you will be notified by your Jint contact.

3.6 Approval of Microsoft API Permissions

Access level required for this step: Global Administrator.

Access the Advanced > API Access section in the SharePoint admin console, or
directly via the URL:

https://<your-tenant>-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/webApiPermissionManagement

Then approve each pending request:

For more details on this step, please refer to Approval of Permissions.

3.7 Approval of Jint API Permissions

Allowing access to Jint APIs enables you to use our services directly within SharePoint. These permissions are necessary to validate the user’s identity and act with those rights.

Required permission:

• API name: Jint Contribution Center
• Requested permission: Access_as_user

Optional permission:

• API name: Jint Translator
• Requested permission: user_impersonation

This authorization is only necessary for Translator features and is not required if you have not subscribed to this product.

To allow an additional permission: Allow access to Jint Translator to be able to access our translation service. For information on how to authorize the permission, consult the article Approval of Permissions.

3.8 Authorization of Jint Service Addresses

Access level required for this step: Network Administrator

This step is only necessary if you filter the addresses accessible from your Microsoft 365 tenant. Jint usage will be impossible if you cannot access our services. If you perform filtering on authorized addresses, you must add the following addresses and all their subdomains to your authorized address list:

Addresses:

• cdn-mozzaik.azureedge.net
• authentication-api-mozzaik.azurewebsites.net
• clientsettings-api-mozzaik.azurewebsites.net
• newshub-api-mozzaik.azurewebsites.net
• mozzaik365.net

Subdomains:

• cdn.mozzaik365.net
• config.mozzaik365.net
• translator.mozzaik365.net
• newshub.mozzaik365.net
• contribcent.mozzaik365.net
• api.mozzaik365.net
• clisettings.mozzaik365.net

Following our name change, you will also need to add the following addresses and subdomains:

Addresses (upcoming):

• cdn-Jint.azureedge.net
• authentication-api-Jint.azurewebsites.net
• clientsettings-api-Jint.azurewebsites.net
• newshub-api-Jint.azurewebsites.net
• jint.io

Subdomains (upcoming):

• cdn.jint.io
• config.jint.io
• translator.jint.io
• contribcent.jint.io
• newshub.jint.io
• api.jint.io 
• clisettings.jint.io 

4. Using the Jint Solution

Jint is properly configured and deployed on your Microsoft environment! You can
now build your Digital Workplace experience using our components and
features.

The Jint WebParts components address business needs through
configurations. The same component, through its configuration, can cover different needs.

Feel free to consult the Jint documentation on our help center to discover our
features and the various solutions we enable you to implement!