-
Notifications
You must be signed in to change notification settings - Fork 446
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
Invite emails directly when creating a conversation #4937
Labels
Milestone
Comments
Yeah, also mentioned in #2874 (comment) |
nickvergessen
changed the title
It should be possible to add/invite users directly by entering their email address when creating a conversation, after guests have already been allowed to join via a public link
Invite emails directly when creating a conversation
Jan 11, 2021
nickvergessen
added
1. to develop
enhancement
feature: api 🛠️
OCS API for conversations, chats and participants
labels
Jan 11, 2021
Thanks for the link! |
Well someone needs to extend the API to accept a list of invitees, and change the frontend to also find emails and then either do an individual request per email or send them on the new creation api with the invitee list |
github-project-automation
bot
moved this to 🧭 Planning evaluation (don't pick)
in 💬 Talk team
Oct 23, 2024
nickvergessen
moved this from 🧭 Planning evaluation (don't pick)
to 📄 To do (~10 entries)
in 💬 Talk team
Oct 23, 2024
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Expected behaviour
It's all in the title.
We have a lot of 1:1 conversations with external participants. For this purpose, the conversations are mostly created exclusively. It would be noticeable improvement if the creation dialog allows this form of usage.
Actual behaviour
Currently, I have to go to the sidebar specifically to email invite a participant after the conversation has already been created.
Talk app
Talk app version: (see apps admin page:
/index.php/settings/apps
)v10.0.5
The text was updated successfully, but these errors were encountered: