Account Settings
Profile and security settings for your GridWonk account.
Account settings open as an account settings sheet. The /account/settings route is a helper that opens that sheet and returns to the last authenticated dashboard path recorded in the current browser tab. If no safe dashboard path exists, it opens the sheet on /dashboard; it never follows browser history back to a public page. If browser privacy settings block per-tab storage, a one-use URL signal opens the sheet on /dashboard instead.
The sheet and its account state are loaded only on authenticated dashboard routes.
The current tabs are Profile, Security, Preferences, and Integrations.
Profile Information
| Field | Description |
|---|---|
| First and last name | Editable profile names |
| Email address | Your login email. Changes are submitted through Supabase email verification. |
| User ID | Unique account identifier |
| Account creation date | When your account was created |
| Role badge | Account-level user or administrator label when available |
Password Requirements
Strong passwords must have:
- Minimum length: 12 characters
- Character types: Mixed case letters, numbers, and special characters
- Strength rating: Must be at least "Good" to submit
Strength Meter Levels
| Level | Description |
|---|---|
| Weak | Does not meet minimum requirements |
| Fair | Meets minimum but could be stronger |
| Good | Acceptable security level |
| Strong | Recommended security level |
| Excellent | Maximum security level |
Changing Your Password
- Go to the Security tab
- Enter your current password
- Enter your new password
- Confirm the new password (enter it again)
- Check that strength meter shows at least "Good"
- Click Update Password
Forgot Your Password?
- Log out of the application
- Click Forgot Password on the login page
- Enter your email address
- Check your email for reset instructions
- Follow the link to set a new password
Preferences
The Preferences tab saves:
- Default Organization — Your workspace when you log in. It must be an active, unexpired direct membership; a grant-only client context cannot be selected as the default.
- Email Notifications — Whether GridWonk can send event emails
- Weekly Digest — Whether to receive a weekly activity summary
- Timezone — Saved preferred timezone. Account creation dates currently use the browser timezone.
Workspace colors are shared organization settings. Direct Owners and Admins of developer and utility organizations use Team and logo > Workspace appearance to preview colors and choose Save appearance. See Workspace appearance for schemes and source-color limits.
Integrations
Open Organization integrations from account settings to see setup for the active workspace.
Developers use /console/integrations, utilities use /utility/integrations, and consultants use
/consultant/integrations. The hub separates saved access, effective availability and connection
status. An enabled service can still require credentials, sign-in or platform configuration.
Organization owners and admins can create runtime API keys when API access and self-service key
creation are enabled. Save a new secret when shown; it cannot be retrieved again. Existing
/console/api-keys and /utility/api-keys pages remain available. Set Expires in (days) to
1–365, or leave it blank for no expiry. Ordinary members retain personal connection permissions
and cannot manage organization keys or installations.
MCP setup provides connection guidance for Claude Desktop and Codex Desktop. Complete the client's credentials or sign-in flow; enabling access does not connect a client automatically. Provider approval and live-client acceptance remain separate requirements. Disabling MCP refuses subsequent MCP requests, including already connected apps, while permitted REST calls continue. Disabling API also blocks MCP and new key creation; browser revocation remains available.
Connected apps at /settings/connected-apps shows your connections and their bound workspace.
Revocation stops local access before any retryable provider cleanup. Changing the active workspace
does not retarget an existing connection. See Connected apps.
Utility owners and admins can open Packet submissions from account Integrations to review approved state/program lanes. Accepting a lane requires current utility authority and a qualified reviewer; it does not expose private developer draft reviews.
The account Connected Accounts card shows your individually linked Slack and Microsoft Teams accounts. Connecting
a workspace or tenant to an organization does not link every employee automatically. Ask the bot a
protected product question, then open the secure one-time account link it sends you while signed
into GridWonk. For Slack, a complete command such as /gk requirements duke-energy NC triggers the
account check; a bare /gk requirements command only shows usage help because it is missing the
utility argument. Re-authorize Slack when an administrator asks you to upgrade an older
installation; this replaces legacy plaintext token storage with encrypted installation data.
Salesforce Installed-App Pilot
The separate outbound-only app is in Layer 2 development and remains disabled. Reviewers use their Salesforce identity without individual GridWonk accounts; no Salesforce tokens are stored in GridWonk. The account settings screen, API keys and legacy automation grants cannot enable it.
The private receipt and direct-upload workflow still needs full native verification. Preparation does not start a review. Every expected file needs independent byte acceptance, and a separate unconditional compute gate blocks extraction, optical character recognition (OCR) and model processing. Read-only progress does not start a review or return findings. Navigation may resume an unfailed attempt; an explicit failure report counts once and prevents that attempt's reuse without releasing its physical slot early. Limits remain two imports, two uploads per import, six failed storage attempts and one original 24-hour deadline. Signed results/history, retention/purge and package onboarding remain later layers.
See Salesforce installed application for the distinction between source implementation, native evidence and activation approval.
Salesforce Utility Connector
Utility workspaces also show the Salesforce packet reviews card with Salesforce connections, opening
/utility/integrations/salesforce. The connector is disabled by default and is not ready for
customer activation. A setup screen does not mean its import or MCP operations are available.
In an approved credentialed-connector pilot, reviewers link their own Salesforce accounts. This individual linking is not part of the separate installed app. Utility owners or admins separately approve mappings, enable reviewers, and authorize expiring automation grants. Save a new service secret when it is shown; it cannot be displayed again. Change source-owned answers and files in Salesforce, not through ordinary GridWonk packet editing.
Adding or changing a different reviewer does not interrupt unrelated imports or result deliveries. Changes to a saved operation's own reviewer link, mapping, or service identity/grant stop that work at its next authorization check. Restoring permission requires a new request; old work does not restart automatically. Turning automation off affects service work only; disabling the connection affects all work. Live Salesforce permission checks remain required.
See Salesforce Utility Connector for preparation and access rules.
Public plugin connections
Open Connected apps to see the public plugin's selected workspace and revoke its access. Changing your default workspace does not retarget an existing connection. See Connected apps. Workspace Owners and Admins can open Billing to view prepaid processing when purchases are available.