Skip to main content
This guide is for an organization’s IT administrator. It connects Parlé to your Microsoft 365 tenant in two parts:
  1. Single sign-on (SSO) — let your team sign in to Parlé with their corporate Microsoft accounts.
  2. SharePoint storage — let project agents read and write files in your SharePoint sites.
Do them in this order. SSO comes first because it establishes the link between Parlé and your Microsoft tenant that SharePoint then reuses.
You’ll need: a Microsoft Entra ID (Azure AD) admin role — Global Administrator or Cloud Application Administrator — to grant consent, and SharePoint Administrator (or site owner) for the storage step. In Parlé you must be an Org Admin.

​
Part 1 — Single sign-on with Microsoft Entra ID

Your admin grants the Parlé application permission to verify your users’ identities. After that, anyone in your organization whose email matches your domain can sign in to Parlé with their Microsoft account — no separate Parlé password.
1

Find your tenant details

In the Microsoft Entra admin center → Overview, copy your Tenant ID and note your primary domain (e.g. contoso.com).
2

Grant consent to Parlé

In Parlé, go to Org settings → Organization → Single sign-on and click Connect Microsoft. You are redirected to Microsoft and asked to consent to Parlé signing your users in. Approve it on behalf of your organization.
3

Configure the connection in Parlé

Back in Org settings → Organization → Single sign-on, enter:
  • Tenant ID — from step 1.
  • Email domain — the domain your users sign in with (e.g. contoso.com). Parlé uses this to route matching users into your organization automatically.
Then toggle Enable single sign-on on.
4

Test it

Sign out, then on the Parlé login page enter a corporate email address. A Sign in with Microsoft button appears. Complete the Microsoft prompt — you should land back in Parlé, signed in.
New users: the first time a colleague signs in with Microsoft, Parlé creates their account automatically and places them in your organization — as long as their email domain matches and you have an available seat.
Single sign-on requires the Business plan or above. If your plan is downgraded, Microsoft sign-in stops working at the next login and users fall back to email/password.

​
Part 2 — SharePoint as project storage

Parlé accesses files using its own application identity, scoped to only the specific SharePoint sites you grant — never your whole tenant. The agent can then read and write project files even when no one is actively online. Deleted files go to your SharePoint recycle bin, where your normal retention and recovery rules apply.
You’ll need the Business plan or above. SharePoint storage is available on the Business plan and above. You must also have completed Part 1 (single sign-on) first — SharePoint reuses the Microsoft tenant captured during SSO setup, so there is no tenant to enter here.
1

Enable SharePoint for your organization

Org Admin, once. In Parlé, go to Org settings → Files & search → SharePoint, enter your SharePoint host (your SharePoint domain, e.g. contoso.sharepoint.com), and click Enable SharePoint. Until this is done, SharePoint will not appear as an option in any project’s storage settings.
2

Pick the SharePoint site

Copy the URL of the site that will hold a project’s files, e.g. https://contoso.sharepoint.com/sites/ClientDelivery.
3

Grant Parlé access to that site

Because Parlé uses least-privilege, site-scoped access, each site must be granted explicitly, once per site, by a SharePoint Administrator or Global Administrator. See the two methods below.
4

Connect the site to a Parlé project

Open the project → Project settings → Storage, choose SharePoint, paste the site URL from step 2, and click Resolve. Parlé resolves the site and lets you pick the document library, then browse its folders and click into the one you want the project rooted at. Stay at the library itself to use the whole library. Then Save.
5

Parlé verifies the connection

It lists the folder you picked before saving. If it cannot reach the site, or the folder is not there, you see an error naming the problem — the most common cause is that step 3 has not been completed for this exact site yet, and the Grant Parlé access button appears alongside the error so you can fix it there and then.
Files the agent creates appear in that SharePoint folder; files your team adds there are visible to the agent’s tools.

​
Granting a site — the easy way

Skip ahead to step 4 and connect the site. When Parlé finds it has not been granted access, it offers a Grant Parlé access button:
  • If you are a SharePoint or Global Administrator, click it, sign in with Microsoft, and confirm. Come back and press Resolve again.
  • If you are not, the same button gives you a link to send to whoever is. They do not need a Parlé account. When they have approved it, press Resolve again.
Parlé uses that administrator’s own sign-in to record the permission and then discards it. It never sees a password, and it gains no access beyond the one site being approved.

​
Granting a site — the manual way

If the button is not available, or your IT team prefers to script it. You will need Parlé’s application ID — your Parlé contact provides this.
Tenant reuse: because you set up single sign-on in Part 1, Parlé already knows your tenant — SharePoint connects to the same Microsoft 365 organization automatically, and never asks you for a tenant ID.

​
SAML single sign-on (Microsoft Entra)

If your Entra directory is set up for SAML 2.0 rather than the OIDC sign-in above, use the Microsoft SAML single sign-on card in Org settings → Organization → Single sign-on. Microsoft OIDC and Microsoft SAML can both be enabled at once.
1

Register Parlé in Entra

The card shows an Identifier (Entity ID) and a Reply URL (Assertion Consumer Service URL), unique to your organization. Create an enterprise application in your Entra tenant and enter those two values. You can also show the service provider metadata on the card.
2

Tell Parlé about your directory

Enter your Email domain and Microsoft tenant ID, then give Parlé your identity provider’s metadata: either an HTTPS Federation metadata URL (Parlé re-reads it periodically, so a rotated signing certificate keeps working) or the pasted federation metadata XML (you must paste it again when the certificate rotates). The identity provider entity ID is optional and normally read from the metadata.
3

Enable it

Tick Enable Microsoft SAML single sign-on and save. Members are provisioned into your organization on first sign-in.
To make SAML or OIDC the only way to sign in, see Requiring single sign-on.

​
Using a Microsoft Teams channel

A Teams channel’s Files tab is just a folder in SharePoint, so pointing a project at a channel is the same flow as above — you just need to know which site the channel lives in. That depends on the channel type: To find the right site URL, open the channel in Teams → Files tab → ⋯ → Open in SharePoint. Copy the site URL from your browser’s address bar — the part up to and including /sites/<name>, without the /Shared Documents/... tail.
A private or shared channel needs its own grant. It is a separate SharePoint site, so granting the parent team’s site does not cover it. If verification fails for a private channel, this is almost always why.
Renaming the channel is safe. Parlé binds to the folder itself, not to its name, so renaming a channel — or moving its folder — does not break the project. Deleting the folder does: the project’s Storage settings will show “needs reconnecting”, and an admin re-picks a folder to fix it. Parlé deliberately will not fall back to another folder that happens to have the old name, because a new folder reusing that name could belong to a different client.

​
Troubleshooting

Still stuck? Contact Parlé support with your organization name and the site URL you are connecting.