Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Admin can remove another admin from the organization

オープン
  • 何か問題がありますか？
#6,314 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
authorization

調査の方向性

The report says the membership API edit queryset permits active organization admins to manage memberships and the delete safeguard only protects the last active admin; it names no files or tests. Start by tracing the membership API's edit queryset and deletion safeguard, then check existing permission tests. Done means an organization admin cannot remove another admin, while a web admin can revoke admin membership.

索引モデルが issue の本文から書いたものです。

説明

bug

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

An organization admin can remove another admin from the organization. This action should be restricted because it changes the user's organization membership and strips administrative access.

Errors and logs

No application error is expected when removing an admin membership. The organization membership DELETE endpoint returns HTTP 204 when the removal succeeds. The backend allows active organization admins to delete memberships, and its safeguard only rejects deletion when the target is the organization's last active admin (HTTP 400). It does not block deletion based on the target's admin role when another active admin remains.

Expected behavior

An admin should not be able to remove another admin from the organization. Only a web admin should be allowed to revoke organization membership for admins.

User-facing consequences

This allows unauthorized removal of administrative access, which can destabilize the organization, reduce administrative coverage, and create a situation where a user is unexpectedly removed from the organization without proper control.

Steps to reproduce

  1. Sign in as an organization admin.
  2. Navigate to the organization SHARING tab.
  3. Find another user whose role is Admin.
  4. Choose the option to remove the user from the organization.
  5. Observe that the request succeeds with HTTP 204 and the target admin's membership is deleted, as long as another active admin remains. If the target is the last active admin, the request is rejected.

Context

The membership API's edit queryset allows active organization admins to manage memberships, including memberships whose target role is Admin. The delete safeguard only preserves at least one active admin; it does not prohibit one admin from removing another. This report reflects the current backend behavior rather than a client-side error.

AI usage

The bugs were gathered by a human and later turned into issue descriptions with the help of an AI assistant. The assistant was used to draft the wording and structure of the report, and the final text was reviewed and adjusted for accuracy based on the supplied bug summary.

主要言語
Python
スター
192
フォーク
310
平均マージ
2日 10時間
マージ済み PR（30日）
66

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

learningequality/studio のほかの issue

learningequality/studio の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。