> 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/account-and-team/user-roles.md). # User roles in Mobly Every Mobly user has a role that determines what they can see and do. Roles are set when a user is created and can be updated by a Mobly admin later. This article explains what each role means in practice — what they see in the app, what controls they have, and how lead visibility works. ## The roles There are two roles you'll work with: | Role | Common label | Who has it | Where they work | | --------------- | -------------- | -------------------------------------------------------------- | --------------- | | **Mobly Admin** | "Admin" | Your team lead, RevOps owner, or whoever runs Mobly day-to-day | Hub + mobile | | **Client** | "Rep" / "User" | Event marketers, sales reps capturing leads | Hub + mobile | Mobly also uses additional internal roles for its own staff and data partners. Those aren't assignable by your admin and aren't covered here. ## What each role can do ### Client (the default rep role) A Client can: * Capture leads in the mobile app at events they're assigned to * View leads they've captured, and leads on events they're assigned to * Edit lead details, add qualifier values, notes, and descriptions * Engage with leads (call, email, text, send content) * Edit their own profile (name, email, calendar links, photo, social links) * Delete their own account A Client **cannot**: * Add other users * View events they aren't assigned to * Configure qualifiers, sequences, integrations, or other org-wide settings * See the Users tab in the Hub ### Mobly Admin A Mobly Admin can do everything a Client can, plus: * Add, disable, and reactivate users (manually or via CSV) * Send welcome emails so new users can complete sign-in * Assign users to events and configure event details * Set up integrations (CRM, MA, Slack) * Configure qualifiers and sequences * Edit any user's profile fields (name, email, calendars) * See all leads and events across the org For most orgs, one or two people are admins — usually the person who owns Mobly internally. A few things are kept out of customer-admin hands and require a Mobly CSM: * **Changing a user's role** — promoting a Client to Mobly Admin, or demoting an Admin to Client * **Sending password reset emails on behalf of another user** — your users can still reset their own password via the **Forgot your password?** link on the login page (see [Having login issues?](/help-center/account-and-team/having-login-issues.md)) * **Enabling org-wide features** like SSO/SAML, Pulse, and other product surfaces ## How lead visibility works Mobly's lead visibility model is **role + event assignment**: * **Admins see everything** in the org — every event, every lead. * **Clients see leads on their assigned events.** Their My Leads view scopes further — see [My Leads](/help-center/the-hub/working-with-leads/my-leads-sales-rep-view.md). There are no per-lead access controls today. If a Client is assigned to an event, they can see all leads captured at that event (not just their own scans). If you need a rep restricted to only the leads they personally captured, that's the **My Leads** filter — but it's a view filter, not a permission boundary. ## Changing a user's role Role changes are handled by Mobly. To promote a Client to Mobly Admin (or vice versa), contact your CSM with the user's name/email and the role you want them set to. Most requests are turned around the same day. ## Related articles * [How to add users](/help-center/account-and-team/how-to-add-users.md) * [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) * [My Leads — the sales-rep view of the Hub](/help-center/the-hub/working-with-leads/my-leads-sales-rep-view.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/account-and-team/user-roles.md?ask=&goal= ``` `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.