Invite people to an organization by email
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- angular, typescript
- Domain
- authentication, backend-api-design, frontend
Research direction
Start by reading the design referenced for the Organization → Invitations section, then trace the existing organization, account verification, and audit flows in the control plane and web UI. Implement invitation creation, acceptance, resend, and cancellation around the stated role, expiry, verified-email, single-use, and audit requirements. Done means each acceptance criterion is covered; the issue does not name files or tests.
Written by the indexing model from the issue text.
Description
Track
C: control plane, W: web UI
Scope
- Organization → Invitations section from the design: invite an email with a role, expiry, resend and cancel.
- Accepting requires an account with a verified email; the invitation is single use.
Acceptance criteria
An invited person who signs up or signs in joins with the given role; expired or reused invitations are refused; every step is audited.
Depends on
—
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 197
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from shipkeepdev/shipkeep
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
shipkeepdev/shipkeep#295 ·
Maintainers usually reply within 1 day
-
good first issue priority:P2 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
shipkeepdev/shipkeep#212 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority:P3 track:web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
shipkeepdev/shipkeep#144 ·
Maintainers usually reply within 1 day
-
documentation good first issue priority:P3 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
shipkeepdev/shipkeep#143 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority:P3 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
shipkeepdev/shipkeep#142 ·
Maintainers usually reply within 1 day
All issues in shipkeepdev/shipkeep
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
[prefer-expect-resolves] autofix leaves a stray ")" when the awaited expression is parenthesizedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jest-community/eslint-plugin-jest#2052 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Wallet functions throws TypeError when the wallet has no account IDPossibly taken @Medhansh-741 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hiero-ledger/hiero-sdk-js#4781 · 1 comment ·
Maintainers usually reply within 1 day