[FR] Members management improvements (API/deactivation)

Offen

#516 erstellt am 18.9.2025 0 Kommentare 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 5/5
Geschätzter Aufwand: Über eine Woche
Anfängerfreundlichkeit: 25/100

Issue-Typ: Feature
Klarheit: Muss geklärt werden
Aktivitätsstatus: Veraltet
Tech-Stack: typescript
Bereich: api, authentication, authorization

Rechercherichtung

No files, tests, or entry points are identified in the issue. Start by getting a maintainer decision on whether the scope is the admin API, activity-based management, or both; the work is ready to begin once the selected behavior and acceptance criteria are defined.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Feature

Hey 👋

Context

We use Sourcebot EE, with a SSO login.

However, as SCIM is not available, old organization members are not deleted automatically, which may lead to security issues (they may not be able to log-in, but API key might still be active), as well as taking up seats for Sourcebot EE.

Deleting members must currently be done manually or through the DB directly.

Suggestion

As implementing LDAP/SCIM can be cumbersome, both for developers and Sourcebot administrators, here's some suggestions that provide a good compromise:

Admin Members API: Create a admin-only REST API for user management (possibly related to #101?) that would:
- Allow admin scripts to list/disable/delete users
- Nice to have: Support batch operations for efficiently managing multiple users
- Nice to have: Properly documented with #101
Activity-based User Management:
- Implement a configurable system to automatically disable users after a specified period of inactivity
- Allow administrators to set custom thresholds (30/60/90 days?)
- Nice to have: Users disabled through inactivity would be automatically re-enabled upon successful SSO login
- Nice to have: Include options to notify users before automatic disabling

Let me know what you think or if you need more details/context!

Cheers, Gabriel

Vorherrschende Sprache: TypeScript
Sterne: 3.9k
Forks: 374
Ø Merge: 21 Std. 18 Min.
Gemergte PRs (30 T.): 39

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sourcebot-dev/sourcebot

[bug] Search result hydration performs duplicate repository lookups within the same chunk Offen

bug triage needed

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100

sourcebot-dev/sourcebot#1681 · 1 Kommentar · Erstellt am 22.9.2026
Linux ctags build instructions in CONTRIBUTING.md are missing build dependencies Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100

sourcebot-dev/sourcebot#1633 · Erstellt am 05.9.2026
Generic Git URL configs keep percent-encoded repo names Offen

bug

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

sourcebot-dev/sourcebot#1384 · 4 Kommentare · Erstellt am 29.6.2026
MCP ask_codebase rejects explicit languageModel: getLanguageModelKey includes displayName which the MCP schema doesn't expose Offen

ask_sb bug

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100

sourcebot-dev/sourcebot#1137 · 4 Kommentare · Erstellt am 20.4.2026
[bug] GitHub App installation tokens (ghs_) are rejected by the credential preflight Offen

bug triage needed

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100

sourcebot-dev/sourcebot#1661 · 1 Kommentar · Erstellt am 16.9.2026

Alle Issues in sourcebot-dev/sourcebot