Multi-use invitations #433

Open
opened 2026-05-21 11:36:24 -05:00 by spin-drift · 1 comment
spin-drift commented 2026-05-21 11:36:24 -05:00 (Migrated from github.com)

Currently, invitations are single-user, and also require the admin to enter all user details except for password/passkey.

It would be nice if invitation links could be created that bypass SIGNUP: TRUE and/or SIGNUP_REQUIRES_APPROVAL, but otherwise allow for multiple users to onboard with them.

Perhaps this could be configured with a specific number of uses, but an MVP would simply allow unlimited signups while the link is marked active.

This would allow admins to block signup from the public, but allow it for users where links can be shared through private means.

Currently, invitations are single-user, and also require the admin to enter all user details except for password/passkey. It would be nice if invitation links could be created that bypass `SIGNUP: TRUE` and/or `SIGNUP_REQUIRES_APPROVAL`, but otherwise allow for multiple users to onboard with them. Perhaps this could be configured with a specific number of uses, but an MVP would simply allow unlimited signups while the link is marked active. This would allow admins to block signup from the public, but allow it for users where links can be shared through private means.
mv-fs commented 2026-06-14 21:06:21 -05:00 (Migrated from github.com)

I would also love this feature. I had planned to invite a group of friends to use one of my services, but was stopped in my tracks by having to register each of them one by one, especially not knowing their details beforehand.
Fixed use count, infinite uses, and SIGNUP_REQUIRES_APPROVAL bypass are all necessary imo

One could also think about making the send invite compatible with multiple receiver addresses for a given link and auto-counting the remaining uses based on the number of recipients and decrement it when one successfully signs in

I would also love this feature. I had planned to invite a group of friends to use one of my services, but was stopped in my tracks by having to register each of them one by one, especially not knowing their details beforehand. Fixed use count, infinite uses, and SIGNUP_REQUIRES_APPROVAL bypass are all necessary imo One could also think about making the send invite compatible with multiple receiver addresses for a given link and auto-counting the remaining uses based on the number of recipients and decrement it when one successfully signs in
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
adam/gate#433
No description provided.