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

Add granular user permission settings

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
csharp
領域
authorization, backend-api-design

調査の方向性

Start by reading the existing MCP/OAuth scope handling and the current app/API authorization policies; the issue does not name specific files or tests. Then map how organization memberships and the new Svelte system/settings area fit the proposed permission model. Done means administrators can manage persisted permissions, restricted users are blocked server-side, existing access stays compatible, and tests cover permission and OAuth scope intersections.

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

説明

Summary

Add general user permission settings so Exceptionless can grant users more granular access than today’s broad user/admin roles, and use that model as the long-term foundation for app, API, MCP, and OAuth authorization.

Why

The MCP/OAuth work introduces granular scopes such as projects:read, stacks:read, stacks:write, and events:read. The normal app/API still mostly uses broader roles like user, client, and global. Users have asked for more security controls for their users, and we should avoid building parallel permission systems for MCP/OAuth and the main app.

Proposed scope

  • Define a durable organization/user permission model.
  • Store permissions per user per organization or membership, rather than only on OAuth clients.
  • Add management UI in the new Svelte system/settings area.
  • Make normal app/API authorization respect those permissions while preserving existing behavior by default.
  • Ensure OAuth scopes cannot grant more access than the signed-in user actually has.
  • Align MCP tools, OAuth API access, and app/API authorization around the same permission concepts over time.

Suggested first pass

  • Keep default behavior backwards compatible: existing users retain their current access unless permissions are explicitly restricted.
  • Start with coarse but useful permissions that map to current MCP/OAuth scopes:
    • projects read
    • stacks read
    • stacks write
    • events read
    • administrative/system settings access, if needed separately
  • Add server-side enforcement before relying on UI-only restrictions.
  • Avoid replacing all existing controller policies in one PR; migrate high-value surfaces first.

Acceptance criteria

  • Organization administrators can view and edit user permissions in the new UI.
  • Permissions are persisted and included in authorization decisions.
  • Existing unrestricted users continue to behave as they do today.
  • Restricted users cannot access disallowed API/app functionality by direct API calls.
  • OAuth/MCP authorization is bounded by both requested scopes and the signed-in user’s permissions.
  • Tests cover default compatibility, restricted access, allowed access, and OAuth scope + user permission intersection.
主要言語
C#
スター
2.5k
フォーク
508
平均マージ
2日 17時間
マージ済み PR（30日）
40

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

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

exceptionless/Exceptionless のほかの issue

exceptionless/Exceptionless の issue をすべて見る

似ている issue

C# の issue をもっと見る

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

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