> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/managing-events/how-to-remove-a-user-from-an-event.md).

# How to remove a user from an event

Sometimes a rep gets assigned to an event they shouldn't be on — wrong team, switched roles, no longer attending. You can unassign them from that specific event in the Hub without disabling their account or touching other events they're on.

\* This article is only relevant to Mobly Admins (with access to the Hub) \*

## Remove a user from an event

1. In the Hub, go to **Events** and click into the event.
2. Switch to the **Users** tab on the event detail page.
3. On the user's row, open the **⋮** action menu and click **Remove**.
4. Confirm in the dialog: *"This action will remove the user from the event, but the leads will remain available."* Click **Yes, Remove User**.

You'll see a toast confirming the user was removed. They lose access to that event in the mobile app immediately — no app restart needed.

## What happens to their leads

**Leads they captured at that event stay with the event.** Removing the user is a permission change, not a data delete — the captures they already made are preserved, attributed to them, and continue to sync to your CRM as normal.

## Adding them back

If you removed someone in error or they need access again, re-add them via the same event detail page — see [How to assign users to an event](/help-center/the-hub/managing-events/how-to-assign-users-to-an-event.md).

## Remove from one event vs. disable the user

These are different actions for different situations:

|                   | Remove from event                                                  | Disable user                                                     |
| ----------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------- |
| **Scope**         | One specific event                                                 | Org-wide                                                         |
| **Effect**        | User loses access to that event only; stays active everywhere else | User can't log in; cleared from all future events                |
| **Past captures** | Preserved                                                          | Preserved                                                        |
| **Reversible**    | Yes — re-assign them                                               | Yes — reactivate, then manually re-assign to events              |
| **Use when**      | One-off mistake, role shuffle, rep not attending this event        | Person leaves the company or no longer needs Mobly access at all |

For the full disable flow, see [What happens when a user is disabled](/help-center/account-and-team/what-happens-when-a-user-is-disabled.md).

## Related articles

* [How to assign users to an event](/help-center/the-hub/managing-events/how-to-assign-users-to-an-event.md)
* [What happens when a user is disabled](/help-center/account-and-team/what-happens-when-a-user-is-disabled.md)
* [How to add users](/help-center/account-and-team/how-to-add-users.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getmobly.com/help-center/the-hub/managing-events/how-to-remove-a-user-from-an-event.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.