Docs
Help Center

Email Notifications

Automated emails GridWonk sends and when you receive them.

Salesforce setup and email

The utility Integrations tab also links to the default-disabled Salesforce setup page. That link does not change email preferences or enable applicant notices. Salesforce result delivery is utility-internal and separate from the notice-email workflow.

Overview

Notification recovery does not alter email delivery or preferences. The bell's read/dismiss updates confirm an authorized notification was matched; a removed or inaccessible item is explained and the list is refreshed, while already-read items and an empty mark-all-read remain valid successes.

GridWonk sends automated emails to keep you informed about account activity, organization changes, and requirement updates. Emails are sent from notices@gridwonk.com; the visible product name follows the active brand configuration, so local legacy-branded environments may still show the legacy name during the transition.

Email Types

EmailWhen SentRecipients
Account Setup InvitationWhen a GridWonk administrator creates or reinvites an approved account that has not signed inNew or reinvited user
WelcomeWhen your account is activated for an organizationNew users
Organization InvitationWhen an admin invites you to join an organizationInvited user
Change AlertWhen a monitored utility's interconnection requirements changeSubscribed organization members
Weekly DigestWeekly summary of platform activityActive organization members

Welcome Email

Sent when your account is created and associated with an organization.

Contains:

  • A greeting with your name
  • The name of the organization you have been added to
  • A link to open your dashboard
  • Contact information for getting access changes

Subject line: Welcome to GridWonk - [Organization Name]

Account Setup Invitation

Sent when a GridWonk administrator creates an approved account or reinvites an approved user who has not signed in yet.

The single-use GridWonk application invitation lasts 30 days. When you accept it, GridWonk creates a separate short-lived authentication handoff to confirm identity and complete account setup. Reinviting revokes the earlier unused setup invitation.

Subject line: Complete your GridWonk account setup

Organization Invitation

Sent when an organization admin invites you to join their team.

Contains:

  • The name of the person who invited you
  • The organization you are being invited to join
  • Your assigned role (Viewer, Member, Admin, or Owner)
  • An Accept invitation button with a unique link
  • A 30-day expiration date for the single-use organization invitation

Organization invitation links are managed by GridWonk separately from Supabase authentication links. After you choose Accept invitation, GridWonk creates a short-lived authentication link to confirm your identity and then consumes the organization invitation. Password-reset, magic-link, and email-verification links keep their shorter security expiration.

Subject line: Invitation to join [Organization Name] on GridWonk

Change Alert

Sent when GridWonk's change monitoring system detects that a utility has updated its interconnection requirements or procedures.

Contains:

  • The utility name and state
  • When the change was detected (date and time in UTC)
  • A summary of what changed
  • An impact assessment describing how the change may affect your applications
  • A link to review the full change details in the platform

Subject line: Requirements change detected: [Utility Name]

Weekly Digest

A periodic summary of activity relevant to your organization, sent once per week.

Contains:

  • A greeting with your name
  • A week label identifying the reporting period
  • A summary paragraph of the week's highlights
  • Individual activity items, each with a title, description, and optional link to the relevant page
  • A link to open your dashboard

Subject line: GridWonk weekly digest - [Week Label]

Delivery Details

For deficiency notices, Sent means the email provider accepted the message, not that it reached the recipient's inbox. Requesting a send first saves a frozen delivery request; queued, retrying, held and provider-accepted-but-finalizing progress are shown separately. Retries keep the same email and delivery key. Do not resend a held or uncertain request. The dependent safe-send release requires separate foundation activation and does not change notification preferences.

The dependent receipt layer stores verified provider email events separately. A delivered receipt is provider delivery evidence, not proof that a person read the message; bounce or complaint evidence does not undo the notice's saved status or trigger another send. Unknown message IDs remain unlinked until they can be matched to a unique accepted request. This adds no receipt viewer or new email preference. Provider configuration and production activation remain held for separate approval.

Automated emails are sent from notices@gridwonk.com. Replies go to support@gridwonk.com. If you are not receiving emails, check your spam or junk folder and add notices@gridwonk.com to your contacts or allowlist.

Deficiency notice emails sent by utilities to applicants are also delivered from this address. Those emails contain the full deficiency list, response deadline, and the active product branding.

Customization

Use Account Settings → Preferences to turn email notifications on or off, enable the weekly digest, and set your timezone. Some transactional or security emails may still be sent when needed for account access, invitations, or compliance workflows.

Slack account linking is managed separately under Account Settings → Integrations and does not change your email notification preferences. Its secure account-link prompt is delivered in Slack rather than by email.

In-App Notifications

GridWonk also has an in-app notification bell. The inbox supports mark-read, mark-all-read, dismiss, and an unread count that refreshes about every 30 seconds while the page is visible and online. Hidden and offline tabs pause checks. Email preferences and in-app notifications are related, but they are not the same delivery channel.

When an accepted utility intake lane receives a formal packet, qualified reviewers receive a durable in-app receipt linked to the application. Private developer packet reviews send no utility receipt. This receipt does not add an email type.

If sign-in expires, the bell clears its outdated count and offers sign-in in another tab. Your workspace remains open; return after signing in or choose Try again. Service failures are shown as failures, not as an empty inbox. If the account or organization changes in another tab, notifications pause rather than showing a different workspace's data. Save unsaved edits before choosing the offered workspace reload. Updates that are refused or unavailable do not appear successful. If GridWonk requires acceptance of updated legal terms, notifications also pause. Save your work, accept the current terms, then reload the workspace before trying the bell again.

For utilities where GridWonk has turned on procedure source monitoring, the bell also shows Public page may have changed alerts to the utility's reviewers, developers who follow that utility, and GridWonk admins. Review document opens the document where your organization reviews procedure documents. These alerts are in-app only.

New client access (when enabled)

When a client creates a new usable grant for your consulting organization, eligible active members receive a persistent bell alert. If email delivery is enabled, each recipient also receives an individual service email with the client, consulting organization, access level, project scope, and expiration. These channels are disabled by default until rollout is approved.

This is not an invitation: sign in with your existing account; no invitation acceptance or client password is needed. You can discover the alert after your next login even if you never open the email or another organization is selected. Signing in again does not send another email. Older grants and people who join the consulting organization later are not backfilled.

The bell is available in the shared header and in Console and Utility workspace controls. Opening it does not mark alerts read. Use Mark read, Mark all read, or Dismiss; these choices persist across sign-ins and devices. View client access opens Consultant Access without switching organizations automatically. Select your consulting organization if needed, then find the client and choose Switch.

Your role and the grant both limit available actions. A Viewer remains read-only. Revoked or expired grants and inactive memberships no longer appear in the actionable inbox. A stale email link cannot restore access. See Access Grants for navigation and troubleshooting.

On this page