A private invite was forwarded. What should the host do?

Replace the invitation if the problem is who can join next. Remove a member if the problem is someone who has already joined. Blocking changes what one player sees; it does not remove that person's access.

Tales Ahead is in private testing, with no public App Store download yet, as checked on 16 October 2026. This guide describes the current group controls. Check app availability before planning a download.

Choose the control that matches the problem

• A link reached people you did not intend to invite: the host can replace the invitation. Older links and codes stop admitting new members; existing members keep their access.
• A person who should no longer participate has joined: the host can remove that member. Removal also invalidates the current invitation.
• You want to hide another member's content from your own view: block that member. Other people can still play with them.

The Support page explains host controls, blocking and joining. A current invitation permits joining without an account; it does not verify who the person is. The privacy page describes the shared content and membership data stored by the service.

If the invitation travelled further than you meant

Here is a fictional example. Alex hosts a weekend board and sends its invitation to the people who agreed to play. Someone forwards it to a larger chat. Alex wants the original group to continue, while stopping further joins through that invitation.

In the current app, the host can choose “Replace invitation” from Group options and confirm. The confirmation says older invitation links and codes stop working while existing members keep their access. Send the replacement privately to intended participants who still need to join. Members already in the group do not need to join again just because the invitation changed.

Ask people to delete the forwarded message if they can. Replacing the invitation is the service control that stops new joins through the old one; deleting a message alone cannot establish that every copy disappeared.

Share invitations only with people who want to play. Keep them out of screenshots, public posts and support messages. The group rules ask organisers to respect anyone who wants to stop.

If someone has already joined

Continue the example: Alex notices an unexpected member. Replacing the invitation would leave that membership active. The host must remove the membership if its access should end.

Check with the intended participants before deciding who to remove. Nicknames are optional and are not verified identities. Avoid sharing private group details with an unfamiliar participant to establish who they are.

Removal invalidates the current invite as well as ending that membership's access. Removal does not automatically show a usable replacement. To invite someone else afterwards, the host can choose “Replace invitation” and create one. Give it only to the intended people: a removed person could join again under a new membership if someone gives them the new invitation. The controls cannot prevent recipients from forwarding a replacement.

Removing a member does not undo changes they made to the title or predictions. If the content needs changing too, agree on the replacement with the group: saving an edit clears everyone’s marks. The prediction guide explains that agreement.

Ending access does not recall content someone has already seen or copied. Avoid sensitive information in the board in the first place. “Private group” describes limited access, not a promise that other members cannot keep its contents.

When hiding content is the immediate need

Any member can block another member, including the host. Under Around the board, open the options beside that person and choose Block player, then confirm. Their nickname and progress disappear from your roster, and the current title or predictions they last changed are hidden for you. Other people can still play with them; blocking does not stop them seeing the group.

Hidden predictions cannot be marked. Edit shared predictions is disabled while a title or prediction is hidden. Under Blocked players, Unblock asks you to confirm Unblock player and makes that content visible again. Keep the block if you prefer not to reveal that content. A guest can leave, and a host can delete the group for everyone. The exit guide explains those choices and saved copies.

If Alex has already blocked the unexpected member, the current app lists them under Blocked players with an Unblock button only. To reach Remove from group in that person’s roster options, Alex would first have to unblock them, revealing their content again. If that is not comfortable, reporting while they remain blocked or ending the group are available choices. Removing them still does not undo their title or prediction edits.

To send a concern for operator review, open Group options, then Report content. Describe the concern briefly, stay within the form’s limit and choose Send report. The app shows Report received after a successful submission. Reporting stays available while content is hidden, but it does not automatically remove content or end anyone’s access. Support explains blocking and reporting.

Keep the reason brief and avoid invite codes, membership tokens, private exports and unnecessary personal details. The service stores the reason, group identifier, reporting member identifier and submission time for up to 31 days, even if the group is deleted; a handled report may be deleted sooner. The privacy page describes report storage.

These control labels and the blocked-player removal path come from an owner inspection of the current app and API source on 16 October 2026. They are not a real-device or production-group test. Shared actions need a connection; if an action fails or its outcome is unclear, check the refreshed group before relying on it. The connectivity guide explains saved copies and uncertain saves.

For Alex's forwarded invitation, the first question remains whether the unwanted access is still a possible join or an existing membership. Replace the invitation for the former; use member removal for the latter, then keep any replacement private.