Organizations
Organizations let teams publish widgets under a shared @org-slug scope instead of personal scopes. Multiple members can collaborate and publish widgets that appear under your organization’s namespace.
What are Organizations
When you publish a widget as an individual, it appears under your personal scope (e.g., @username/widget-name). Organizations give teams a shared publishing namespace, for example @my-team/widget-name. Any member with the right permissions can publish widgets under the organization scope.
Each account can create one organization. The limit is per-account and is enforced at creation time.
Creating an Organization
Go to Organizations
Dashboard > Organizations tab
Create Organization
Click the Create Organization button
Name your org
Slug is auto-derived from the name
The organization name is used to derive a URL-safe slug automatically; spaces and special characters are replaced with hyphens. The slug becomes your publishing scope (e.g., @my-team) and cannot be changed after creation.
Members and Roles
Organizations have three roles that control what each member can do:
Owner
Full access. Can manage members, update settings, publish widgets, and delete the organization.
Admin
Can invite and remove members, manage member roles, and publish widgets under the org scope.
Member
Can view organization details. Cannot publish widgets under the org scope (only Owner and Admin can publish).
Invitations
To invite a member, go to the org detail page and click Invite Member in the Members tab. Enter their email address and select a role.
The invitation is sent to that email address. The invitee must have a GlassHome Hub account with a matching email address to accept; there is no open sign-up path from an invitation link. Invitations expire after 48 hours. To accept, the invitee visits their Hub account and accepts from the pending invitations list.
Owners and Admins can change member roles or remove members from the org detail page.
Who can update existing widgets
Once a widget is published under an org scope, any Owner or Admin can re-publish (update) it by running bun widget publish with the org scope. Members with the member role cannot publish. See Publishing Widgets.
Ownership transfer
There is no automated ownership transfer UI. If you need to transfer org ownership to another member, contact me directly.
Publishing under an Organization
When you run bun widget publish, the CLI prompts you to select a publishing scope if you belong to any organizations:
? Select publishing scope:
❯ @your-username (personal)
@my-team (organization)
Widgets published under an organization scope appear with the org’s scope tag in the Widget Browser (e.g., @my-team/widget-name).
Managing Organizations
The Settings tab in the org detail page lets Owners and Admins rename the organization. The slug is read-only after creation.
Danger Zone
- Leave Organization. Members and Admins can leave an organization. You will lose publishing access under the org scope.
- Delete Organization. Only the Owner can delete an organization. Widgets already published under the org scope will remain available in the Widget Browser but cannot be updated.