Managing invitations to projects
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When an admin invites a user to a project,
- An admin should be able to see the list of pending invites
- Resend invite should resend the email with the link to join the project.
- An admin should be able to remove an invite
- The invite should expire after 2 weeks and can be refreshed by a new invitation. (We should not be creating duplicates)
- If the invite was removed or expired, the invited user should not be able to join the project. They should get a message "Can't join the project, please contact the project Administrator)
- Any Admin can manage an invitation.
- On the collaborations page, All users can see the list of users but only admins will be able to add new users to the project (or see the add/invite user button)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the project invitation flow and the collaborations page described in the issue. Review how pending invites, resend and removal actions, expiry, duplicate prevention, and join validation are currently handled. Done means all checklist behaviors work, including admin-only management and the specified message for removed or expired invites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100