# No se pueden asignar usuarios a temas ni a publicaciones

**URL:** <https://meta.discourse.org/t/unable-to-assign-users-to-topics-or-posts/414310>\
**Category:** Support\
**Tags:** assign\
**Created:** [9 Octubre, 2026 04:47 UTC](https://meta.discourse.org/t/unable-to-assign-users-to-topics-or-posts/414310 "2026-10-09T04:47:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [14 Octubre, 2026 09:07 UTC](https://meta.discourse.org/t/unable-to-assign-users-to-topics-or-posts/414310/5 "2026-10-14T09:07:22Z")

</div>

gracias por el informe @here - el problema se solucionará con

> <https://github.com/discourse/discourse/pull/44564>
>
> Previously, the assign modal searched \`/u/search/users\` with the assign-allowed …groups as \`groups\[\]\`. Core rejects that with a 403 when the searching user can't see one of those groups' members, and the chooser silently showed the 403 as "No matches found". Admins were unaffected. The first search sometimes worked because it ran before the suggestions, and their groups, had loaded.
> 
> This change adds an \`/assign/search\` endpoint. It searches the users and groups the current user can actually assign on the target, using the same \`AssignmentPermissions\` rules that \`Assigner\` enforces. The modal now uses the core \`EmailGroupUserChooser\` pointed at that endpoint, replacing the custom \`AssignmentChooser\`. The duplicated assignable-user scopes are merged into \`AssignmentPermissions.assignable\_user\_ids\`.
> 
> \`/assign/suggestions\` now returns \`groups: \[{ name, full\_name }\]\` instead of \`assign\_allowed\_on\_groups\`/\`assign\_allowed\_for\_groups\`.
> 
> Stacked on #44563.
> 
> https://meta.discourse.org/t/414310

---

_[View the full topic](https://meta.discourse.org/t/unable-to-assign-users-to-topics-or-posts/414310)._