GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — API for inviting and removing Organization members · Issue #20828 · pypi/warehouse

API for inviting and removing Organization members #20828

New issue
Copy link
New issue
Copy link
Open
Open
API for inviting and removing Organization members#20828
Copy link
Labels
APIs/feedsblockedIssues we can't or shouldn't get to yetIssues we can't or shouldn't get to yetfeature requestorganizations

Description

@cjames23
cjames23
opened on Oct 27, 2026
Issue body actions

Before you submit

  • I searched existing issues and found no duplicate.

What problem does this feature solve?

Organization owners need a way to invite, remove, and change the roles of members through an API. Right now every change has to be made by hand. This requires that on a larger Organization, Owners remember to manage changes when they occur.

Describe the solution you'd like

Proposed Endpoints:
Each endpoint uses API_KEY auth and needs the same permission as the matching UI action:

list members and pending invites
invite a user with a role, revoke an invite, change a role, remove a member
The rules would be the same as in the UI: invitees still accept by email, the last Owner can't be removed, and every action is recorded in the org's event history.

Open questions
Should the key belong to an Owner's account, or to the organization itself?
Should team membership be included?

Additional context

No response

Activity

  1. cjames23
    added
    feature request
    requires triagingmaintainers need to do initial inspection of issuemaintainers need to do initial inspection of issue
    on Oct 27, 2026
  2. JacobCoffee
    added
    blockedIssues we can't or shouldn't get to yetIssues we can't or shouldn't get to yet
    APIs/feeds
    organizations
    and removed
    requires triagingmaintainers need to do initial inspection of issuemaintainers need to do initial inspection of issue
    on Oct 27, 2026
  3. miketheman
    marked this as blocked on Oct 28, 2026
    • [META] Determine API design for performing maintainer actions #13409
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    APIs/feedsblockedIssues we can't or shouldn't get to yetIssues we can't or shouldn't get to yetfeature requestorganizations

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.