Skip to main content

Organization publishers

An organization is a durable shared Publisher identity. Its permanent namespace appears in Blueprint IDs such as @productatlas-labs/incident-response. Organization-owned Blueprint Drafts and Releases remain with the organization when individual members leave.

Create an organization

Open Organizations from your signed-in account navigation, then choose Create organization. Creation requires:

  • a permanent available lowercase publisher namespace;
  • a public display name;
  • an optional description; and
  • an optional absolute HTTPS website without credentials, query parameters, or a fragment.

The creator becomes the first Owner. The public organization profile shows its display information, Owner display names, and available public Blueprint Releases. It never publishes member email addresses.

Roles

Roles are cumulative and are enforced by the ProductAtlas application for both browser and API operations.

RoleCapabilities
ContributorRead and edit private Blueprint Drafts and manage Draft assets.
PublisherAll Contributor capabilities, plus submit Drafts, publish and deprecate Releases, and read publisher analytics.
OwnerAll Publisher capabilities, plus update the organization profile and manage invitations, membership, and roles.

An organization must always retain a final Owner. ProductAtlas rejects an attempt to remove or demote that Owner. Owner promotions, demotions, and removals require a recent sign-in.

Invite a member

An Owner enters the recipient's email and selects Contributor, Publisher, or Owner. The invitation expires after seven days and can be resent or revoked while pending.

The recipient must sign in with a ProductAtlas account whose trusted verified email matches the invitation. The invitation is single-use. After acceptance, the member can select the organization when creating a Blueprint and sees only the actions allowed by their current role.

Ownership and membership

Membership grants access; it does not own the organization content. A Blueprint stores the organization's stable local owner ID, not the account ID of the person who created it. Removing a member immediately removes their organization capabilities without transferring or deleting the organization's Drafts or immutable Releases.

Publisher-authored descriptions, links, and Blueprint content remain untrusted third-party data. Review Trust and safety before following external guidance.