For Consultants
Manage interconnection workflows across multiple clients with GridWonk.
Client processing and account scope
Self-service developer registration and verified utility claims do not enroll a consulting firm or create a client access grant. Continue to use the consultant approval and grant workflow below. Within an authorized client context, new packet processing must also satisfy that client's processing allowance and supported workflow. A grant does not enable native DWG processing or unrestricted chat for a trial or prepaid client workspace.
In an authorized developer-client context, current document checks can produce a partial report before the packet review completes. Treat that report as incomplete coverage, not approval or a submission-ready packet. Client grant scope and utility review authority remain unchanged.
After a permitted, human-confirmed PDF split, the original and its earlier reviews stay in history. Current findings cover the resulting documents and their exact packet set. A read-only grant cannot confirm or recover a split; existing client permissions remain in force.
Client workspace appearance
A client workspace may use its organization's saved colors. Consultant workspaces do not support the appearance schemes, and grant-derived admin access does not let a consultant change a client's appearance. A direct Owner/Admin of the developer or utility client uses Team and logo > Workspace appearance to preview and save it. Colors never change data access or grant scope.
Salesforce pilot access
Consultant grants and platform impersonation do not authorize Salesforce connection administration or substitute for a direct utility employee's linked account. The implemented connector remains disabled, and its captured results also require current Salesforce source access. Ordinary client-grant workflows on this page remain separate.
Who Is This For?
Engineering consultants, interconnection advisors, and firms that serve both utilities and project developers as intermediaries. If you manage interconnection applications on behalf of clients — like DRG Technologies — this guide is for you.
Getting Started
When you work in a developer client's granted project, a released full packet setup can support private review by default, including before the utility joins GridWonk. Private review remains available when Submit is available. That does not authorize formal submission: GridWonk and a real utility representative must accept the exact state and program, and the utility must have an active reviewer. Your existing grant and role limits still apply.
- Contact us for consultant-tier access — Email contact@gridwonk.com to request a consultant account
- Account approval — A GridWonk admin will review and approve your account before you can access any data or features; accept any current legal documents when GridWonk asks you to do so
- Set up your organization — Create your consulting firm as an organization in GridWonk
- Request or receive client access grants — Client organization admins and owners can grant consultant access; GridWonk admins can assist when support access is needed
- Work within each grant boundary — Use available agents and workflows only for the active organization, grant level, and project scope
- Export branded reports — Deliver professional PDF reports to your clients
Utility organizations are provisioned by GridWonk after affiliation review; a consultant cannot
self-claim a utilityId.
Multi-Client Workflow
Notice mutations and dispatch recheck current membership and the exact client grant, including project scope. Pending or held notice delivery blocks conflicting application changes. Use the correct client context and resolve delivery; a cached grant or new send request cannot override the hold.
GridWonk supports consultants who work across multiple clients and utility territories.
The important model detail is that consultants are their own organization type in GridWonk — one of four, alongside utility, developer, and the internal GridWonk platform type. They do not replace the utility or developer on a shared submission row. Instead, they participate through scoped access grants from their client organizations.
Organization Switching
- Each client engagement maps to an organization in GridWonk
- Use Organization and role to switch directly into an available client context without logging out. Find it in the shared header, or near the bottom of the expanded Console or Utility sidebar.
- All validation runs, uploads, and results are scoped to the active organization
- Project and demo deep links are checked against that active context and fail closed rather than switching organizations automatically
- Work for utilities and developers from the same consultant account
- Access is controlled via grants — utility and developer clients can grant your consultant org specific access levels (
read,write, oradmin) with optional project-level scoping and expiration dates
Working for Different Client Types
| Client Type | Your Workflow |
|---|---|
| Project Developers | Upload their IX applications, run validation agents, deliver deficiency reports before submission |
| Utilities | Review incoming applications against utility-specific requirements, flag deficiencies for the utility review team |
Team Coordination
Roles & Permissions
GridWonk uses role-based access control to keep your team organized:
| Role | Capabilities |
|---|---|
| Owner | Full access, billing, org management |
| Admin | Manage members, run all agents, export reports |
| Member | Upload documents, run agents, view results |
| Viewer | Read-only access to results and reports |
Assign roles based on responsibility — give junior analysts Viewer access for QA review, and senior engineers Member or Admin access for active validation work.
Grant-derived access is not the same as direct organization membership. Creating console projects through developer workflows requires direct membership in the active organization; granted access is rejected for that specific mutation. Use write/admin grants for workflows that explicitly support granted mutations, and switch into a directly joined client org before creating a new project.
A write or admin grant does not override your role in the receiving consultant organization. Grant-aware mutations require both an active Member, Admin, or Owner receiving-org role and a write or admin grant. A Viewer remains read-only even when the organization has a higher-level grant.
That means:
- the client org still owns its own workflow rows
- your consultant org works inside the granted scope
- audit and grant rules stay attached to your consultant participation
The optional Combined-PDF split has a stricter applicant-authority boundary than ordinary granted reads. Optional intake features (combined-PDF split, ZIP upload) are on by default and managed per applicant organization by that organization's own admins (platform rollout controls can still narrow availability, and platform-set rows appear read-only on that organization's Features page), so their controls appear only where that organization has them on. A consultant context may see authorized document and split status, but it cannot analyze, confirm, or discard a split—even with a write/admin grant. The applicant developer organization (or a platform administrator) must make the human page-range and role decision.
Responding to a deficiency notice is developer-client scoped. Your consultant home organization does not receive the Start response action. After you switch into a granted developer-client context, the action can run only when your receiving consultant organization still has an active Member, Admin, or Owner user plus an in-scope write/admin grant for that project. Attaching the first corrected document also starts the response automatically, so the response stage is recorded even when nobody presses the button first. After an authorized resubmission, the corrected immutable package returns to the receiving utility as Pending. The utility starts its whole-packet review with Screen Selected or an authorized integration. The application moves to Screening before work starts and Screened when complete; a failed start or run restores the earlier status once no other utility review is active. The applicant-side action does not act with utility review authority, and client grants do not gain new permissions.
Audit Trails
Every action in GridWonk is logged:
- Who uploaded which documents
- Which agents were run, when, and by whom
- Validation results and any changes over time
This makes it straightforward to demonstrate diligence to your clients.
Reporting & Deliverables
PDF Reports
Export professional, branded validation reports for client delivery. Reports include:
- Compliance scorecards with pass/fail status per requirement
- Identified deficiencies with remediation guidance
- Document classification and extraction results
Before delivering a report or notice, confirm that no document re-review is pending. GridWonk hides findings tied to replaced bytes and prevents packet-wide notice drafting until the current document versions have been reviewed.
Coming Soon: Custom branding (your firm's logo and colors on exported reports) is planned for a future release.
JSON API
For consultants who build their own tools or dashboards, the API Reference documents the org-scoped results currently available through the public API, including deficiency-report and application query/sync surfaces. It does not expose every internal validation result or workflow. Integrate only the documented surfaces that your organization key can access. API access and usage limits are provisioned by GridWonk per organization — they are not configurable from organization settings. Repeated organization-setting updates may return HTTP 429; wait before retrying.
The browser organization-management routes use the same fail-closed input boundary: grant and organization mutations reject bodies over 32 KiB, member changes over 16 KiB, and switch requests over 8 KiB before database work. Project-scoped grant lists are capped at 500 identifiers.
Bulk Processing
Utility workspaces already support batch intake, queue filtering, multi-select screening, and CSV export. Consultants can use those workflows when the active organization and grant level allow utility workspace access.
Consultant-specific reporting across multiple client organizations is still constrained by organization switching and grant scope. Switch to the correct client context before uploading, screening, exporting, or running agents.
Next Steps
- API Reference — Programmatic access for custom integrations
- Access Grants — How membership, grant level, scope, and action rules combine
- Help Center — Detailed feature documentation
- For Developers — Understand the developer workflow you'll be supporting
- For Utilities — Understand the utility workflow you'll be supporting
Discover new client access
When enabled, a new client grant creates a persistent bell alert for eligible existing direct members of your consulting organization. Email can be enabled separately; no invitation acceptance is needed. Alerts remain visible in other organization contexts, and View client access opens Consultant Access without silently switching organizations. Existing grants and later member joins are not backfilled. See Access Grants for the full workflow.