Customer-controlled
by design.
DGH is designed around customer-owned Microsoft 365 services and connections. This page describes the product boundary, permission model, and important limitations for the current release candidate.
Where DGH data lives
Routine DGH workflow records, configuration, review copies, history, intake records, and governed documents live in the customer’s Microsoft environment, primarily SharePoint Online and Power Automate. Teams and Standard Approvals provide notifications and human decision experiences. Microsoft Forms is optional.
Connections and service ownership
Connection references are bound to customer-owned Microsoft connections during deployment. A customer-controlled service account is used for provisioning and protected runtime operations. Customers are responsible for that account’s lifecycle, authentication controls, license entitlement, and continuity when staff or credentials change.
Protected review content
DGH keeps the source file separate from the review copy. Reviewers act on a protected copy associated with the request. Publication verifies the recorded review-copy evidence before using those bytes for controlled publication. This is intended to reduce the risk that content changes after review but before publication.
Permission model
DGH applies group-scoped SharePoint access to its business containers. The configured audience can access the records intended for requesters/reviewers, while protected writes and administrative helpers are restricted. Tenant administrators, SharePoint/site administrators, and the DGH service account remain privileged.
What DGH does not claim
- DGH is not a per-document information-barrier product. Do not use one DGH audience group as proof of document-by-document confidentiality.
- SharePoint business history is not described as an immutable or tamper-proof regulatory ledger.
- DGH does not independently establish HIPAA, GxP, SOX, ISO, or other regulatory compliance. Customers must configure the surrounding Microsoft environment and governance controls to their own obligations.
- Automatic cross-document supersession and training/acknowledgment tracking are outside the current release.
Source document boundary
Source documents must be direct file URLs on the configured SharePoint site. OneDrive links, external web locations, and sharing-link formats are not supported by the current publication path.
Support access
AppParallax does not require routine access to customer content to operate DGH. When support is requested, a customer may voluntarily provide diagnostic information or authorize scoped access under the applicable support/implementation agreement. Do not send passwords, secrets, access tokens, patient information, or confidential business documents through the public website form.
Security responsibilities
| AppParallax / DGH | Customer |
|---|---|
| Provide the packaged workflow, setup helpers, validation checks, documented permission model, guarded request/publication processing, and product documentation. | Choose the tenant/site, configure audience groups, bind customer connections, manage Microsoft identities/licenses, review tenant policy, back up business data, and validate the final production permission model. |
| Document known product boundaries and avoid claiming per-document confidentiality or an immutable regulatory ledger. | Decide whether DGH’s group-scoped model is appropriate for the organization’s data classification and compliance requirements. |
For personal-information handling by the product and support process, see the DGH Privacy & Data Handling Notice.