Ad-hoc guest access for voice channels

(#1449) Feature Open: Planned community voice

Current problem

Sometimes I want to invite people to a voice channel for a short, spontaneous session without asking them to create a permanent Fluxer account first. A common example would be an online game: I'm playing with a few people who do not use Fluxer, and I would like to invite them to a voice channel just for the current match or gaming session. At the moment, they would need to go through the normal registration flow and provide an email address, even though they may only want to use the voice channel for an hour or two. For this kind of temporary access, creating a permanent account feels unnecessary and adds enough friction that people may simply not want to join. There is already a temporary-account / guest-access concept described in fluxer-meta #3 as part of Events / Calendar. However, the use case described there appears to be tied to a scheduled event. For spontaneous voice sessions, having to create a calendar event first would add unnecessary overhead. The guest access itself would be useful independently of Events.

Proposed change

I would like to be able to create a temporary guest invite directly from a voice channel. For example: Right-click voice channel → Create guest invite The invite could have options such as:
  • Expiration time (for example 1 hour, 3 hours, 24 hours, or custom)
  • Maximum number of uses
  • Optional invite password
A guest opening the link should not have to create a normal Fluxer account or provide an email address or account password. Ideally, the flow would be as simple as: Open invite → choose display name → join voice channel The guest should only have access to the voice channel they were invited to, rather than becoming a normal member of the entire community or instance. The temporary guest session/identity should expire automatically. Once it has expired, the temporary guest account itself should also be permanently cleaned up rather than remaining indefinitely as a disabled or unused account. If a guest decides that they want to stay on Fluxer, there could optionally be a way to convert the guest into a normal account by providing an email address and password. Permanent accounts would therefore continue to use the normal registration/account model.

Additional information

Related roadmap item: https://github.com/fluxerapp/fluxer-meta/issues/3 That issue already describes temporary accounts / guest access in the context of Events / Calendar, including allowing someone without an existing Fluxer account to join a linked voice channel temporarily. This proposal is not intended to replace or duplicate the event-based flow. The distinction is that this use case is ad-hoc and independent of the calendar: Event-based guest access: Create event → link voice channel → invite guests for the event Ad-hoc guest access: Open voice channel → create temporary guest invite → share link The underlying temporary guest mechanism may of course be shared between both features. I asked about this distinction in the Fluxer development server, and Hampus suggested opening a separate Ideas discussion describing the use case, which could be merged with the existing work later if appropriate. Some examples where ad-hoc guest access could be useful:
  • Online gaming sessions
  • LAN parties
  • Quick calls with people who do not use Fluxer
  • Workshops or small events
  • Temporary project groups
  • Support or troubleshooting calls
  • Short-lived community voice sessions
The main goal is to make joining a temporary voice session nearly frictionless without turning every guest into a permanent account on the Fluxer instance.
  1. Hampus changed the status from Under consideration to Planned

2 comments

Sign in with Fluxer to comment and vote.
Comment by @michelleDeko
RexSystem 4 votes originally by @michelleDeko on GitHub
I would maybe even suggest to add guest access per guild in general. Not just for voice chat but also for text chat (or at least the voice channel's text chat like teamspeak does it) This would also allow users who don't know fluxer yet and don't want to create yet another account to actually test it without the need of an account.
Comment by sodiboo
sodiboo 3 votes
This "guest access" should also extend to people with accounts. Again, with the gaming use case, very recently i've been in a situation where me and a group were in a voice call (on Discord, forgive me!) playing an online game with one random stranger. We thought their vibe was cool, so we wanted to chat on Discord and party up for the next game or two. But we didn't want to add this person to our friend group's guild without further screening. So, we used a group chat, moved the call there, and invited the person to the group chat. It would be cool if we could invite them as a guest temporarily to the call session (or for an event organized in a private server) and they could "participate" temporarily in our guild's activities, without actually being a permanent member at any point in time. A different use case for this is game development. I'm a game developer. I organize with my devbestie in a discord guild. At one point, we wanted to invite a user to test something one-off. This led to restructuring all the existing internal chats into being locked behind roles, and we had to create a separate "public" area of the guild where our playtester could chat and join a call. It would be nice to instead allow this user to join our call that one time, without granting access to the rest of the otherwise-private guild, because at the end of the day it's an internal guild for development activities and not for public use. permission-wise, I'm imagining that a "guest" is someone who doesn't inherit anything from the @everyone role (whether it be an ephemeral account or not). and while they're present, they would instead be granted access to channels with per-account overrides. and "letting a guest stay" would be equivalent to assigning them the @everyone role. anyone without @everyone would be prominently marked with a GUEST tag near their name, which potentially indicates they haven't read the rules (?) (but that's okay, an admin invited them and can keep them in line) this idea of "someone without @everyone permissions" feels similar to a different setup I've done with a verification bot on discord. in order to not make the channel list filled with locks (not very aesthetic!), i had a bot automatically assign an "Unverified" role to all new members, which would remove "read messages" from all other channels. then, they'd have to go through our onboarding (linking with the main service this community was attached to), and only then would they be allowed to see channels from @everyone. it would also be nice if people who never verified were not there permanently to begin with; what i really want for this use case is to Only create "guest invite" links to this community, and my bot would be in charge of assigning @everyone to users who completed our custom onboarding.