# "Arrive at topic" invite permissions issue **URL:** \ **Category:** Bug\ **Created:** [September 29, 2026, 9:42pm UTC](https://meta.discourse.org/t/arrive-at-topic-invite-permissions-issue/413611 "2026-09-29T21:42:42Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\ **Post date:** [September 30, 2026, 6:50pm UTC](https://meta.discourse.org/t/arrive-at-topic-invite-permissions-issue/413611/2 "2026-09-30T18:50:52Z")
I can see the issue, thanks for the reproduction steps… I think this should fix the issues for the linked topic too. > > > Reported here: https://meta.discourse.org/t/arrive-at-topic-invite-permissions-i…ssue/413611 > > "Arrive at topic" invites to a topic in a restricted category are failing unless the invite also adds the person to one of that category's editable groups. If the category was only open to groups like \`trust\_level\_0\` or \`logged\_in\_users\`, creating the invite returned a 403, even for admins, although the invited user would be able to see the topic after signing up. > > This change counts the automatic groups every invited user joins (\`logged\_in\_users\` and \`trust\_level\_0\` through \`default\_invitee\_trust\_level\`) when deciding whether an invite can target the topic, so these invites now work without adding a group. The problem was that we were missing the fact that all users are part of `trust_level_0` and `logged_in_users` (and `default_invitee_trust_level`) after redeeming an invite… the invite was requiring the invitees to be added to those groups in the invite process, but it’s not possible because they’re automatic groups. --- _[View the full topic](https://meta.discourse.org/t/arrive-at-topic-invite-permissions-issue/413611)._