Manage Group Settings

An owner or authorised admin updates the group's configuration.

Who Can Do This

The group owner can change any setting. Admins can change the following:

  • Members who can create a ride — always changeable by admins
  • Group name — if Allow admin to change group name is enabled
  • Group description — if Allow admin to change description is enabled

All other settings are owner-only.

Steps

  1. Go to the group settings screen.
  2. Update the desired settings.
  3. Save changes.

To regenerate the invite code (owner only):

  1. Go to the group settings screen.
  2. Tap Regenerate Invite Code.
  3. Reshare the new invite link or QR code.

Rules

The following settings can be changed:

Setting Who can change
Members who can create a ride Owner/Admin
New users require approval to join Owner only
Invite via link or QR code Owner only
Allow admin to change group name Owner only
Allow admin to change description Owner only
Group type Owner only
Base location Owner only
Group name Owner; admin if permitted by settings
Group description Owner; admin if permitted by settings

Validation rules apply when updating name or description:

  • Group name must be between 3 and 100 characters.
  • Description must be non-empty and can be up to 500 characters.

  • Base location uses autocomplete — the user searches and selects from suggested cities or neighbourhoods. Free-text entry is not accepted.

  • Only the owner can regenerate the invite code or change the invite-enabled setting. The entire invite management section is hidden from admins.

  • Admins can access and share the current invite link and QR code from the group details page when invites are enabled, but cannot regenerate the code.
  • Disabling invite links immediately deactivates all existing invite URLs. Any previously shared links will stop working.
  • Regenerating the invite code also immediately invalidates all previously shared links and QR codes. Both encode the same invite code, so a new link and QR code are generated together and must be reshared.
  • Switching the group type to private removes it from the discovery feed immediately. Switching back to public makes it discoverable again. Pending discovery-based join requests from before the switch are not cancelled; they remain and can still be approved or rejected normally. (A group whose owner has lapsed is read-only and cannot have its settings changed at all — see below.)
  • Changing the base location updates the group's position in proximity-based discovery results immediately to reflect the new location. Pending join requests submitted before the location change are unaffected — they remain valid and can still be approved or rejected normally.
  • Enabling join approval applies only to new join requests. Existing members are not affected.
  • Disabling join approval immediately approves all pending join requests. If any requests are pending when approval is disabled, the owner is first shown the full list of pending requesters and must confirm before the change takes effect. This gives the owner the opportunity to remove unwanted requesters from the list before bulk-approving.
  • When a group is switched from public to private, any discovery-based join requests that were pending before the switch remain valid. Requesters can still view and cancel their request from the Requests tab or via the notification they received when they submitted it. The group no longer appears in the discovery feed, but the request is not cancelled.
  • Changing ride creation permissions takes effect immediately for all future rides. Free members cannot create rides regardless of this setting — ride creation always requires an active subscription.
  • Settings cannot be changed while the group is archived. They can be changed again once the group is reactivated. See Archive a Group.
  • Settings cannot be changed while the group is frozen (owner lapsed). They can be changed again once the group returns to active. See Frozen (owner lapsed).

What Happens Next

Changes are applied immediately. A group name change triggers a notification to all members. All other changes — description, base location, ride-creation permissions, and other settings — are applied silently. Members see the updated information the next time they open the group.

Failure Cases

  • Name too short or too long: Validation is inline. The name field shows an error if the name is under 3 or over 100 characters. The save button is disabled until the name is valid.
  • Description empty or too long: Validation is inline. The description field shows an error if it is empty or over 500 characters. The save button is disabled until the description is valid.

Status: partially-live. Backend PATCH /groups/:groupId and invite-code regeneration endpoints are complete. The groups module has not yet been built in the frontend.