Select sites and libraries
Start with a designated product-documentation library rather than indexing an organization’s full intranet.
Integrations SharePoint
SharePointPlanned
SharePointPlannedSharePoint answers without exposing the intranet.
Plan a SharePoint knowledge connection for selected support libraries. Keep internal sites and customer-facing knowledge separate.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Knowledge
What we’re planning to connect.
- 01SharePoint
- 02Planned connection
- 03Message support
Review inherited access
A document available to staff may still contain internal notes. Customer-facing approval is a separate decision.
Maintain source context
The proposed connector should retain document location and revision information so support owners can review answers.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected sites and libraries
Approved document content
Access and revision metadata
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose a support library and have its owner identify approved material and exclusions.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Move a document into a restricted location and confirm it is no longer eligible for customer answers.
Before you connect
SharePoint integration questions
Can I connect SharePoint to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Move a document into a restricted location and confirm it is no longer eligible for customer answers.