The SharePoint integration lets people in your workspace use your organization's SharePoint documents in BEAMON without uploading them by hand. Setting it up is a one-time task for a BEAMON workspace admin, together with a Microsoft administrator for your organization.
This article explains how to approve BEAMON for your Microsoft organization, what that approval covers, and how to roll the integration out to your team. For day-to-day use, see Import and Manage SharePoint Documents in BEAMON.
- Before you start
- Step 1: Approve BEAMON for your organization
- What the approval covers
- Per-user browsing and import
- Background sync
- What this means for access to imported documents
- Step 2: Tell your team
- Removing access
- Occasionally asked questions
Before you start
You need:
- A BEAMON account with admin rights in your workspace.
- A Microsoft administrator for your organization. Granting the approval requires one of the following Microsoft roles: Global Administrator, Privileged Role Administrator, or Cloud Application Administrator.
The Microsoft administrator does not need a BEAMON account.
Step 1: Approve BEAMON for your organization
- In BEAMON, go to Configuration → Integrations and find the SharePoint tile.
- Choose how to grant the approval:
- You are the Microsoft administrator: click Connect. You are redirected to Microsoft, where you sign in and approve the request.
- Someone else is the Microsoft administrator: click Copy link and send the link to them. They open it, sign in, and approve. The link works without a BEAMON account and expires after 7 days.
- After approval, Microsoft shows a confirmation that access has been granted and that people in your workspace can now connect their own accounts.
Back on the Integrations page, the SharePoint tile shows your Microsoft tenant and the connection date.
If the approval fails, the Microsoft page states the reason. The most common cause is that the person approving does not hold one of the Microsoft roles listed above.
What the approval covers
The approval grants two distinct kinds of access. Microsoft lists both on the approval screen.
Per-user browsing and import
Each person connects their own Microsoft work account. When they browse SharePoint in BEAMON, they see only the sites, document libraries, and folders their own Microsoft permissions allow. A person cannot import a folder they cannot open in SharePoint.
Background sync
BEAMON's application identity reads SharePoint content to keep imported folders up to date. This is what allows an imported folder to stay current independently of any single user's account or sign-in status.
What this means for access to imported documents
Once a folder has been imported into BEAMON, its documents behave like any other documents in that BEAMON space. Access is governed by BEAMON permissions, not by SharePoint permissions.
In practice: if a person can see the documents area a folder was imported into, they can use those documents in Assist, even if they would not be able to open the same folder in SharePoint.
Consider this before rolling the integration out if your organization relies on SharePoint permissions to separate information – for example for confidentiality walls between matters or teams. Guidance for these cases is to restrict who can import folders, and to import only into spaces where every member is entitled to see the content.
Step 2: Tell your team
Once the approval is complete, people see a banner on the Documents page prompting them to connect their Microsoft account, so no announcement is strictly required. A short note in your team channel still helps, along with a link to Import and Manage SharePoint Documents in BEAMON.
Removing access
Removing BEAMON's access to SharePoint has two separate parts:
- In BEAMON: removing the SharePoint connection removes SharePoint access for all users in your workspace. Imported documents already in BEAMON are not deleted.
- In Microsoft: this does not withdraw BEAMON's approval inside your Microsoft organization. A Microsoft administrator removes it separately in the Entra admin center, under Enterprise applications.
Occasionally asked questions
Why does the SharePoint tab not appear for users?
Confirm that the approval in Step 1 completed successfully. The tab appears only once the organization-level approval is in place.
What if a user reports that they cannot see a site a colleague can see?
This is the permission model working as intended for browsing. BEAMON shows each person what their own Microsoft account can access. The user's SharePoint administrator grants access to the site in SharePoint; it then appears in BEAMON.
What do I do when the approval fails?
Check that the person approving holds one of the required Microsoft roles: Global Administrator, Privileged Role Administrator, or Cloud Application Administrator.
For anything else, contact support@bryter.io.