Organizations

Create or join a workspaceCopy Anchor Link

When self-service registration is available, verified users who accept the current terms and privacy policy can create a developer workspace. Repeating the same creation request resumes that workspace. Joining an existing team requires an invitation to your own email address; a shared email domain does not grant membership. Utility affiliation requires independent staff review. See account and workspace setup.

Owners and Admins of developer and utility workspaces can open Billing from the organization selector when purchases are enabled. Trial eligibility remains tied to the workspace and its original creator. Switching the website's workspace does not retarget an existing public-plugin connection; manage that separately in Connected apps. Available prepaid packs and payment history belong to the selected workspace. Purchases happen on the website; a connected plugin cannot purchase credits or change billing.

Switching OrganizationsCopy Anchor Link

Use the Organization and role selector in the header to switch between organizations where you have a direct membership and client contexts available through an active access grant. The selector shows the active organization and persona before you open or change project data. A granted client context is not a direct membership. When you switch, the dashboard updates to the data allowed by that membership or grant.

Test and demo organizations carry a Synthetic label in the selector. The label does not change membership, grant scope or access permissions.

Approval, membership, and grant scope are not enough when GridWonk asks you to accept updated legal documents. Save any work, accept the current documents, then reload before using customer data or workspace actions.

GridWonk still uses one organizations table for all tenant types:

• utility
• developer
• consultant
• GridWonk platform administration

The internal platform label is the canonical gridwonk value after the Batch 8 database rename. The selector presents that organization as GridWonk.

Switching organizations changes which tenant context you are working in. It does not rewrite who owns a shared submission row. The switch writes the canonical GridWonk active-organization cookie, marks the effective audience as resolved for the docs host, and clears the legacy active-organization cookie.

Organization, membership, grant, and switch mutations are parsed only after a route-specific body size check. Oversized requests receive 413 before database work; normal organization and grant updates are limited to 32 KiB, member and invitation updates to 16 KiB, and organization switches to 8 KiB. Field and list limits still apply after parsing.

Project and curated demo deep links are validated against this active context. If the named project is missing, ambiguous, outside the organization, or unauthorized, GridWonk refuses the link rather than switching organizations automatically.

What Changes When SwitchingCopy Anchor Link

Your view updates to show:

• Documents uploaded by your organization
• Deficiency reports for your organization's projects
• Agent sessions run by organization members
• Dashboard statistics for your organization

Every organization has one type — utility, developer, consultant, or the internal GridWonk platform type — and the type, not the role, decides which features exist at all.

What Stays the SameCopy Anchor Link

Some reference data, such as public utility procedure information and queue analytics, may be shared as market intelligence. Customer uploads, validation runs, deficiency reports, and notices remain scoped to the active organization or grant.

Organization RolesCopy Anchor Link

Platform administrators can create a tenant from Admin Console > Organizations > Create Organization. Enter the customer's Owner email to invite that person as the first Owner; the operator is then not added to the organization and supports it from the admin console. If the invitation cannot be sent, the dialog says so and links to the organization, where the Team tab can resend it. Leave the field empty and the creator becomes the first owner. Utility organizations must be linked to an existing utility record that is not already assigned to another organization. Only platform administrators can create a utility organization or set a paid billing tier when creating an organization.

Utility organizations represent real utility affiliations and are provisioned by the GridWonk platform team. An ordinary authenticated user cannot claim an existing utility by submitting its utilityId; contact GridWonk to set up utility access.

Consultant access can also come from grants. Grants may be read, write, or admin level, can expire, and can be scoped to a specific project. Grant-derived access is separate from direct organization membership.

Role is only one part of authorization. The organization type must support the action, and a granted context must also have an active in-scope grant. For mutations through a grant, the receiving user must be a Member, Admin, or Owner and the grant must be write or admin. Some actions, including developer project creation, still require direct membership.

For shared submission workflows:

• the utility organization owns the review queue row
• the developer organization is linked as the applicant on that row
• consultant organizations participate through grants rather than by becoming one of those owner columns

Permission DetailsCopy Anchor Link

This table shows the normal direct-membership floor for features that the organization type supports. It does not override stricter org-type, grant-scope, or action-specific rules.

"Manage organization settings" covers workspace preferences and the workspace Features page, where an admin or owner can turn the Slack and Microsoft Teams assistant transports on or off for the whole organization and connect the organization's Slack workspace or Microsoft 365 tenant. Slack uses its authorization page. Teams uses two steps: install GridWonk from the Teams Store, then send the generated one-time command in a private bot chat and confirm in the browser. The tenant connection identifies the organization; each person still links their own GridWonk account. Which features an organization may control is decided by GridWonk from the platform-wide feature registry; the currently opened chat controls are recorded in an audit history and each change requires a short written reason. A setting made by the GridWonk team takes precedence — the page shows it read-only with a contact-support note rather than offering the toggle. Feature management requires direct admin or owner membership — grant-based admin access does not include it. Platform-managed configuration — API and MCP access, usage limits, and billing status — is provisioned by GridWonk for each organization and cannot be changed from organization settings, even by an owner. Repeated setting updates may return HTTP 429; wait before retrying.

An admin or owner may deactivate and reactivate either platform installation from the same page. A Microsoft 365 tenant already connected to another GridWonk organization cannot be taken over through self-service; contact GridWonk support to resolve the ownership conflict.

A directly assigned Admin or Owner can also enable Assistant skill sets and assign versioned guidance for interconnection research, project coordination, or deficiency review. Assignments are audited and affect Slack prompt guidance only; they add no tools or data access. Grant-derived admin access cannot manage either feature switches or skill-set assignments.

BillingCopy Anchor Link

Direct Owners and Admins of developer or utility workspaces can choose Billing from the Organization and role selector. The page checks current account approval, verified email, membership and legal acceptance before showing that organization's purchase history. Grant-derived client access does not authorize purchases or purchase history.

Purchases are unavailable by default and require separately approved payment configuration. Returning from Checkout is not payment confirmation: credits appear only after verified settlement. A held purchase remains on hold for support review.

Team and logoCopy Anchor Link

Open the Organization and role selector and choose Team and logo to see who belongs to the active organization. Every direct member sees the active directory. Grant-derived access does not open another organization's team.

Owners and Admins also see pending invitations and manage the team from the same page:

• Invite people by work email with a role and an optional access end date. GridWonk emails a single-use link. A person without an account sets a password first; a person with an account signs in and accepts. The answer is the same in both cases, so the page does not reveal who already has an account. In an organization that GridWonk did not provision, a brand-new account also waits for GridWonk approval.
• Resend a new link, which stops the previous one, or cancel a pending invitation.
• Change role, suspend, reactivate or remove a member. Removing someone ends their access to this organization only; their account and history stay.
• Approve or decline a join request from a person whose email domain matches the organization.

Only an Owner can invite or appoint an Owner, change an Owner's access, or make another member an Owner. An Owner may step down to Admin while transferring ownership. Every organization keeps at least one active Owner, and Owner access has no end date. The last Owner cannot leave, be demoted, suspended or removed, even when two changes arrive at the same time. Every change is recorded in the audit log, and repeated changes may return HTTP 429.

Owners and Admins can also set the organization logo. Enter the company website, and GridWonk shows the logo its logo index has for that website in the selector and on the Team page, or the initials when it has none. GridWonk support can also set a custom https:// image URL, which takes precedence; if it fails to load, the website logo and then the initials appear. Contact support to set or remove a custom image. The website is for display only and never changes the sign-in domain that decides join requests.

Workspace appearanceCopy Anchor Link

Direct Owners and Admins of developer and utility organizations use Team and logo > Workspace appearance. Choose colors in the local preview, then select Save appearance to apply full branding to the organization.

Grant-based admin access does not include this setting. Consultant workspaces do not support these schemes.

1. Save the company website in the logo settings, then choose Find brand colors if more source colors are needed. This reads the public website and supported logo images; it does not apply a scheme.
2. Choose Light, Brand color, or Dark brand. Only the preview changes while you choose.
3. If needed, choose Main brand color, Accent color, and Dark brand color from the source swatches. You cannot enter an unrelated custom color.
4. Select Save appearance to apply full branding for the organization. Cancel restores the saved selection without changing the workspace appearance.

Dark brand is unavailable when the sources contain no usable dark color. GridWonk does not invent a darker shade. Action fills and accents use the selected source colors; readable neutral text and surfaces remain. The dark-sidebar option does not turn on a site-wide dark mode. A saved full-branding scheme keeps its chosen appearance even when a personal dark theme is selected.

Source colors can come from the saved logo.dev brand, the company website, or supported PNG, JPEG, and WebP logo images. Discovery is a limited inspection, so it may miss colors or fail on a blocked website or unsupported image. An unsuccessful discovery or save keeps the saved appearance. If the website or saved appearance changed while you were editing, refresh the card and choose again.

Saving applies the scheme to this organization's developer or utility workspace; other members see it on their next page load. It does not change the sign-in domain. Displayed logos still use the support-approved logo override, the website's indexed logo, or initials. Finding a logo image for color evidence does not approve it as the displayed logo. Contact GridWonk support for a custom logo or to turn off full branding.

Need Access?Copy Anchor Link

Contact your organization admin to be added as a viewer or member. If you work across multiple organizations, ask about multi-organization access and review how grant-based access is decided.

TipsCopy Anchor Link

• Your default organization loads automatically when you log in
• The Organization and role selector shows all organizations and client contexts you can access
• Switching organizations takes effect immediately
• Your personal settings stay the same regardless of which organization you're viewing

New client access alertsCopy Anchor Link

When enabled, eligible existing members of a consulting organization receive a persistent bell notification for a new client grant; email is controlled separately. This is not a membership invitation and needs no acceptance. The alert remains visible when another organization is selected. See Access Grants for navigation, role limits, and notification eligibility.