Managing Members

Organization owners and admins invite members and choose how much Registry and dashboard access each person receives.

Roles

Role	Core access
Owner	Full organization control, including billing, payment methods, payout providers, security requirements, ownership transfer, and deletion.
Admin	Manage members and non-owner roles, organization settings, Registry tokens, webhooks, Marketplace purchases and licenses, and package settings. Organization-plan billing and payout-provider changes remain owner-only.
Maintainer	Publish organization packages, manage supported release operations, and view package analytics. Cannot manage members or organization and dashboard package settings.
Member	Install private organization packages and use shared organization resources. Cannot publish or manage organization settings.

Owners and admins can change a member between Admin, Maintainer, and Member. Ownership changes use the separate transfer flow.

Invite by Username or Email

Open Dashboard > Organization > Members.
Search for an LPM.dev Registry username or enter an email address.
Choose Admin, Maintainer, or Member.
Send the invitation.

The invitation is sent to the selected email address and expires after seven days. The recipient must sign in with that email address to accept it.

A pending invitation is not billed. Acceptance adds the member and updates the organization subscription quantity with proration. If billing synchronization is delayed, it retries automatically.

Invitations cannot be sent or accepted after organization billing has lapsed beyond its grace period.

Invite from a GitHub Organization

Owners and admins can create invitations from a connected GitHub organization:

Select GitHub organization on the Members page.
Install the LPM GitHub App with read-only organization-member access.
Select up to 100 members in one batch.
Choose a default organization role and adjust individual roles when needed.
Create the invitations and share the generated team link.

Each invitation is bound to the GitHub account's immutable user ID. A recipient must connect and sign in with that GitHub account to accept it. Invitations still expire after seven days, and billing begins only as each invitation is accepted.

GitHub import creates one invitation batch. It does not continuously synchronize GitHub membership or roles with the LPM.dev Registry organization.

Remove a Member

Owners and admins can remove another member. An admin cannot remove an owner.

Removal ends the person's organization membership and private-package access, revokes organization-scoped Registry tokens they created, removes organization-provided Pool access, and updates the billed organization seat count with proration.

Admins, maintainers, and members can also leave an organization themselves. An owner must transfer ownership or delete the organization instead.

Transfer Ownership

The target owner must already be an organization member.

Open Dashboard > Organization > Settings > Danger Zone.
Select the target member.
Confirm the transfer.
Ask the target member to accept the emailed request.

The request expires after seven days. Starting another transfer cancels the previous pending request.

When the transfer is accepted:

The target member becomes Owner.
The initiating owner becomes Admin.
Owner-only billing, payout, security, and deletion controls move to the new owner.

The initiating owner can cancel a pending transfer before it is accepted. The target member can decline it.