Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add admin-invite management (track, revoke, resend)

未关闭
#911 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
typescript

调研方向

Start by reading the existing participant invitation flow in ParticipantsController and the Invite model, then trace POST /users (createUser) and its password-reset invitation flow. The issue calls for choosing how to represent deployment-level and study-scoped admin invites, then adding admin-client management to list, revoke, and resend them. Done means pending invitations can be tracked and managed, including identifying admins who have not completed setup.

由索引模型根据 Issue 内容生成。

描述

admin-client backend enhancement

Follow-up to #890.

Currently admins are onboarded via the password reset flow rather than the Invite table. When POST /users (createUser) runs, the backend generates a random password, creates the User row, and sends the invited admin a reset link with adminInvite: true. The admin sets their real password via that link and the token is marked used.

Because the Invite table is bypassed entirely, OrgAdmins have no way to view pending admin invitations, revoke or resend them, or see which admins haven't completed setup. All of that functionality exists for participants via ParticipantsController.

Per @ignatiusm's comment in #890, this looks like a shortcut from when the feature was first built. Making admin invites first-class (tracked, revocable, resendable) would be worth doing.

Considerations

  • Deployment-level admin invites (OrgAdmins invited to the platform)
  • Study-scoped admin invites (StudyAdmins for specific studies)
  • The current Invite model has a required studyId, so it's participant-focused. Would need to either generalise the model or add a parallel AdminInvite table.
  • New admin-client UI to list, revoke, and resend admin invites.
主要语言
TypeScript
星标
4
派生
0
平均合并
14 小时 50 分钟
30 天内合并 PR
5

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Garvan-Data-Science-Platform/ctrl 的其他 Issue

查看 Garvan-Data-Science-Platform/ctrl 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。