PowerShell Setup

Purpose

The planned Merxence-M365-Setup.ps1 helper will support initial IT administrator onboarding and a reusable Drive ID map for HighLevel workflow users. Its actual commands and supported operations still require verification.

Administrator setup establishes the approved connection and resource handoff once. Business users then configure and test each workflow, with IT maintaining credentials and access over time.

Prerequisites

Before using a future reviewed release:

• Agree on the SharePoint sites and libraries with their owners.
• Confirm the product’s authentication method and Microsoft Graph permission requirements.
• Use an approved test environment and a non-sensitive test resource.
• Confirm the release’s supported PowerShell version, modules, and administrator privileges. Those requirements are not yet published.

Inputs

Prepare the intended tenant and application identifiers and an approved site/library inventory. This is a planning checklist, not a confirmed parameter list. The helper’s exact input names, credential method, and resource selection format await review. Keep credentials separate from the Drive ID map.

Safe PowerShell example

Illustrative example only. This code formats fictional data locally; it does not connect to Microsoft 365, discover IDs, grant access, or configure HighLevel. Its values cannot be used in a real workflow.

Drive-ID-map-example.ps1

# Local formatting example only — all IDs below are fictional.
$driveMap = @(
  [pscustomobject]@{ Site = 'Operations'; Library = 'Documents'; DriveId = 'b!exampleDriveId123' }
  [pscustomobject]@{ Site = 'Operations'; Library = 'Products'; DriveId = 'b!exampleDriveId456' }
  [pscustomobject]@{ Site = 'Clients'; Library = 'Client Documents'; DriveId = 'b!exampleDriveId789' }
)
$driveMap | Format-Table Site, Library, DriveId -AutoSize

Use the code block’s copy control to copy this local example. It is separate from the reviewed production helper.

Reviewed script download

The reviewed downloadable helper will be provided after final verification. No production setup script is available to download yet. Use these guides for planning and contact support for version-specific setup guidance.

Version and last updated

Helper version: no reviewed release published. Documentation updated: October 5, 2026. This date is not a script release date.

Expected output

The local example prints the three fictional rows below. The future helper is intended to produce a reusable Drive ID map, but its output fields, export format, and success/error messages still require verification. A formatted table alone does not establish runtime access.

Drive ID mapping table

Site	Library	Drive ID
Operations	Documents	b!exampleDriveId123
Operations	Products	b!exampleDriveId456
Clients	Client Documents	b!exampleDriveId789

Example data only. Site and Library help people understand the mapping. The Drive ID identifies the library and is reused by relevant HighLevel workflow actions that request it. Not every action necessarily needs a Drive ID; exact fields must be verified per action.

See generate your Drive ID map and Drive IDs for mapping and identifier guidance.

IT → HighLevel user handoff

IT will provide the validated map, approved connection context, owner, and review date after setup is verified. Share credentials separately through your organization’s approved secure channel. Workflow users select the appropriate library and use its Drive ID only when the installed action requests it.

Continue with HighLevel user setup and verify setup.

Troubleshooting

• Connection or expired credential: authentication.
• HTTP 403 or permission denied: permissions.
• Wrong site or library: SharePoint access.
• Helper-specific commands and errors: await the reviewed release instructions; do not guess parameters or widen permissions.

Send sanitized details through support. Never email credentials or confidential files.