Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to invite users to a private room based on an invite link. #573

Closed
ara4n opened this issue Mar 30, 2020 · 7 comments
Closed

Ability to invite users to a private room based on an invite link. #573

ara4n opened this issue Mar 30, 2020 · 7 comments

Comments

@ara4n
Copy link
Member

ara4n commented Mar 30, 2020

Rather than inviting users to a private room by their email address, it could be really nice to let them join via an alias but provide a password (or a "magic link").

@dbkr
Copy link
Member

dbkr commented Mar 31, 2020

As in a single-use link or one they could also give to others?

@KopfKrieg
Copy link

I wouldn't make it single use. Single use means I click it, and then it works exactly once. But what if I want to join the conversation later again, or I need to switch to a different browser, or I joined via phone and now want to join via laptop too?

Most conference/chat systems I know allow the link to be used multiple times (and therefore even to share it).

@MurzNN
Copy link

MurzNN commented Apr 6, 2020

As example of UX implementation, we can lookup Skype, that already have invite links to private groups, also allowing joining to room as guest account (only fill name, without registering)!

@MurzNN
Copy link

MurzNN commented Apr 6, 2020

Also we have knock feature PR, that can be combined with invite links, so when user open invite link, he generate "knock" event, and room moderator can accept or reject it.

@hex-m
Copy link

hex-m commented Sep 25, 2020

Here is the issue for the knock feature: element-hq/element-web#14237

@cdauth
Copy link

cdauth commented May 1, 2022

This seems to be the one thing that is still blocking me from migrating from Mattermost to Matrix.

My use cases are that I am part of several loose organizations that have some kind of internal communication infrastructure, such as a private Wiki or a mailing list. For the organization, I want to create a private Matrix space or room. As far as I understand, right now to invite new people to that space/room, they have to provide me with their Matrix username and I have to manually invite them to the space/room. This centralizes the responsibility and power of adding people, which goes against the principles of my organizations. Instead, I would like to generate an invite link that I can share over the internal communication infrastructure of my organizations and that permanently enables people to join the space/room after they have created a Matrix account.

There may be other use cases where it is undesirable for the link to be permanently valid, for example when using a link to invite a single person through another communication channel (such as Signal). Ideally, the UI would allow specifying the validation period of the invite link, and it would list all existing valid invite links along with the possibility to revoke them. But for a start, I believe permanent invite links are the most needed.

@q9f
Copy link

q9f commented Aug 31, 2022

We have been using matrix (vector, riot, element) for many years now for companies internally, but also for larger public communities. It has matured a lot and clients like element are so much more usable today as compared to five years ago; and we really appreciate it.

However, I have to agree with @cdauth that this issue is potentially the biggest pain point in managing communities currently. As a space admin, I need to be able to invite users to a private room without knowing their handles. Currently, you have to ask each individual for their matrix handle which is a drastic overhead for groups of 50+.

An invite link would be the most smooth solution and I hope that this can be implemented soon. ❤️

@t3chguy t3chguy transferred this issue from element-hq/element-web Aug 31, 2022
@element-hq element-hq locked and limited conversation to collaborators Aug 31, 2022
@t3chguy t3chguy transferred this issue from element-hq/element-call Aug 31, 2022
@t3chguy t3chguy converted this issue into discussion #574 Aug 31, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

8 participants