How Group Trip Invite Links Actually Get Everyone In

The usual way group invites break#

Someone starts a group trip. They add three friends to a WhatsApp thread, paste a signup link, and by the second reply someone's asking "wait, is this the right link?" A day later a fourth friend gets forwarded a screenshot of the group chat instead of an actual invite, because nobody remembers where the original link went. None of this is anyone's fault — it's just what happens when "inviting people" is improvised instead of built in.

Lumela treats the invite itself as a feature, not an afterthought bolted onto group creation. That means the code, the link, and what happens on both ends of it are all built to answer the same question a group organizer actually has: how do I get the right people into this trip, without either locking friends out by mistake or leaving the door open to whoever happens to see the link.

The code, and why it looks the way it does#

Every group gets a 4-character join code the moment it's created — something like 7XKT. It's not a slug or a counter; it's drawn with a cryptographically random generator, from an alphabet that deliberately excludes characters people misread over voice or text, like 0/O and 1/I. That matters more than it sounds: a code someone reads out loud on a call, or squints at in a blurry screenshot, still has to resolve to the right characters.

If a code ever leaks somewhere it shouldn't — posted publicly, sent to the wrong chat — a group admin can rotate it from the group's settings. The old code stops working immediately; nobody who's already a member is affected, and nobody holding the leaked code can use it anymore.

A link that knows what device it's on#

Sharing the raw 4-character code works, but Lumela also generates a /join?code= link that does more than a plain deep link. Open it on a phone that already has Lumela installed, and it tries to jump straight into the app's join screen. Open it on a phone that doesn't, and it shows the right call to action for that device — the App Store on iPhone, a direct APK download on Android — with the group's name and member count already visible, so the person knows what they're saying yes to before installing anything.

Here's the part that usually gets missed in apps that build this less carefully: tapping that download button also saves the invite so the app can pick it back up automatically once it's installed, instead of dropping a brand-new user onto a generic home screen with no idea which group they came from. Install, open, and the invite is just... there.

Typing a code doesn't skip the group#

This is the detail worth knowing if you're the one running the group: entering a join code doesn't add someone to the group on the spot. It files a join request. By default a group admin has to approve it; groups can also be set so any existing member can approve new requests, which is useful for a friend group where nobody wants to be the sole gatekeeper.

That one step is what keeps a code that's shared a little too widely from becoming an actual access problem — someone can have the code, and even ask to join, without silently being seated in a trip's shared expenses and locations. Whoever's approving sees exactly who's asking before anyone's in.

Checking before you commit#

Before signing up at all, anyone with a code can preview what they're about to join — the group's name and how many people are already in it — without creating an account first. It's a small thing, but it answers the two questions people actually have when a friend sends them a code: is this real, and is this the right trip.

Who's actually doing the approving#

By default, approval sits with whoever created the group and any other admins — but for a big friend group where one person shouldn't have to babysit a queue of join requests, a group can flip on a setting that lets any existing member approve new ones. Either way, every pending request goes to whoever can act on it as a push notification, not just a badge someone has to remember to check, so a friend waiting to get in isn't stuck for a day because the admin didn't open the app.

Where this fits into planning a trip#

Getting everyone into the same group is step one of a group trip, and the expense splitting and shared planning that follow only work once that step is solid. A code nobody can misread, a link that adapts to whoever opens it, and an approval step that keeps the group intentional — that's the whole invite flow, and it's designed to be the part of the trip nobody has to think about twice.