SecurityResourcesAbout
Log InBook a Demohello@vesence.com
Back to Guides

Features and capabilities

Using Vesence with SharePoint and OneDrive

Updated recently

Vesence can work with SharePoint and OneDrive where access is available.

This lets Vesence use files from the document environment your team already works in, instead of relying only on files uploaded manually into the Workspace.

Use this when the source material, templates, drafts, precedents, or project files are stored in SharePoint or OneDrive.

What the connection is for

The SharePoint and OneDrive connection helps Vesence work with existing file context.

It can help Vesence:

  • Find relevant files
  • Locate project or matter folders
  • Use cloud files as source material
  • Work with templates and precedents
  • Bring documents into the Workspace for analysis or editing where supported
  • Prepare outputs that relate to the same file context
  • Stage changes for user review where supported

SharePoint and OneDrive extend the Workspace with connected document context.

How this relates to the Workspace

The Workspace is the collaboration layer between the user and the Vesence agent.

See: Vesence Workspace for more information.

SharePoint and OneDrive can provide connected source material for that Workspace. This means Vesence can work with the files and folders that already belong to the user's project, matter, team, or organization.

In simple terms:

  • SharePoint and OneDrive are where many source files live.
  • The Workspace is where Vesence works with those files during the task.
  • Vesence can help find, use, and prepare work product from that connected context.

What Vesence can do with SharePoint and OneDrive

Where access and permissions allow, Vesence can help:

  • Search for files by name, topic, party, date, or remembered detail
  • List folders and identify relevant documents
  • Find recent or likely versions
  • Bring files into the working context
  • Compare cloud files with uploaded files
  • Use cloud files as source material for summaries, drafts, or checks
  • Prepare edits or outputs for user review where supported
  • Organize or rename files where the workflow supports it

See the file browser

This is the SharePoint and OneDrive browser inside Vesence. Open My OneDrive or a SharePoint site, move through folders using the breadcrumb at the top, switch between list and grid view, and select a file to use it as source material.

My OneDrive——OneDrive
SharePoint sites——Sites
2 items

When to use connected files

Use SharePoint or OneDrive when:

  • The file already lives in a shared matter or project folder.
  • You need the latest version from a connected location.
  • The task depends on several files in the same folder.
  • You want Vesence to search for precedents or related materials.

If you only need to review a single local file, uploading it manually may be simpler.

How to refer to connected files

When asking Vesence to use SharePoint or OneDrive, describe the file, folder, matter, project, or search target as clearly as possible.

Examples:

  • "Find the latest version of the services agreement in the project folder."
  • "Search SharePoint for NDAs involving this customer."
  • "Use the files in the signing folder to prepare a closing checklist."
  • "Compare the agreement in OneDrive against the version attached to this email."

If several similar files are found, Vesence may ask which one should be used.

Common workflows

Find the right file

Example prompts:

  • "Find the latest version of the agreement in SharePoint."
  • "Search OneDrive for the draft board memo."
  • "Find the folder for this matter."

Work with project folders

Example prompts:

  • "List the documents in this project folder."
  • "Identify which files look like final versions."
  • "Create an overview of the materials in this folder."

Search for precedents

Example prompts:

  • "Search for similar customer NDAs."
  • "Find a precedent services agreement with similar liability language."
  • "Look for prior examples of this clause."

Permissions and access

Vesence can only work with SharePoint and OneDrive files where access is available.

If Vesence cannot find or open a file, it may be because:

  • The file is in a location Vesence cannot access.
  • The user does not have permission.
  • The file name or folder location is unclear.
  • The file has not been made available to the Workspace.
  • The file type is unsupported or restricted.

If this happens, provide a clearer folder, file name, or upload the file directly if appropriate.

Source of truth and versions

SharePoint and OneDrive often contain several versions of similar files.

Tell Vesence which file is authoritative when it matters.

Examples:

  • "Use the file marked final as the source of truth."
  • "Use the most recent version unless there is a signed copy."
  • "Compare the latest draft against the signed PDF."
  • "Use the template in this folder, but use the uploaded term sheet for deal terms."
  • "Ignore archived versions unless needed for comparison."
  • "Use the board-approved version, not the working draft."

This helps Vesence avoid relying on the wrong version.

Staged changes and review

Where supported, Vesence may prepare changes to SharePoint or OneDrive files without publishing them automatically.

This means the user can review the prepared change before it is finalized or published.

Review is important for:

  • Edits to important documents
  • File moves or renames
  • Folder organization
  • Outputs that will be shared with others
  • Any document that may be sent externally or relied on

Before publishing or relying on changes, check:

  • The right file was used.
  • The correct version was edited.
  • Proposed edits are appropriate.
  • Any generated output is saved in the right place.
  • Permissions and sharing settings are appropriate.

Tips for better results

  • Give Vesence the file name, folder name, matter name, or other detail you remember.
  • Tell Vesence whether to search SharePoint, OneDrive, or both.
  • Identify the source of truth if multiple versions exist.
  • Tell Vesence whether archived, signed, or draft folders should be included.
  • Ask Vesence to confirm which file it found before using it for important work.
  • Review outputs and staged changes before relying on them or publishing them.

Related articles