Complete-source review
The release candidate is reviewed as a whole rather than approving isolated snippets or an earlier draft.
Harbor security model
Pierline separates application creation from independent validation, artifact signing, exact-byte verification, and constrained hosting inside SharePoint.
DEFENSE IN DEPTH
The release candidate is reviewed as a whole rather than approving isolated snippets or an earlier draft.
Final review is performed separately from the model and interaction that created the application.
Approval is bound cryptographically to the release artifact and its deployment context.
Harbor checks that the hosted HTML is the same artifact that was approved and has not changed afterward.
The application runs in a sandbox with explicit bridges for supported SharePoint capabilities.
SharePoint and Entra remain the source of truth for identity, site membership, and application data access.
DATA ACCESS
Workshop distinguishes between a private test audience and the people who will use a published application. Connected SharePoint data is presented as an explicit access decision rather than an invisible side effect of code generation.
Harbor mediates supported SharePoint operations, limits unsafe cross-site discovery, and applies policy checks to sensitive write patterns. The purpose is to preserve useful business capability while constraining what an embedded application can do.
If approved application bytes are modified after review, Harbor rejects the artifact. That keeps the security decision attached to what actually runs.
RESPONSIBILITY
Pierline’s controls reduce risk around generated applications, but they work alongside the customer’s Microsoft 365 configuration, site governance, data classification, and user-access decisions.
We can walk through a release from private test page to verified Harbor deployment.