> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/account-and-billing/users.md). # Users ### Permissions overview

Permission	User	Admin
View all leads & accounts	✅	✅
View & edit all Segments		✅
View & edit their own Segments	✅	✅
Access & manage integrations		✅
Acces & manage Clients / agents		✅
Acces & manage lists		✅
Access & manage Users		✅
Access & manage Datasets (sites)		✅
Access & manage their LeadBoards	✅	✅
Access and edit Workflow Automation		✅
Upload Leads	✅	✅

### Ownership We added the Lead ownership concept in LeadBoxer a few years ago, but it somehow got snowed under by new features and other cool stuff. So last month we decided it was time to revamp the concept and make it part of our core feature set again.
Lead Ownership is also saved as a value in the Lead Properties, meaning that: * Lead Ownership can also be used in the filters; using an easy select drop-down of your users. * Lead Ownership is visible in the Lead Card as a separate item (including the timestamp on hover) * Lead Owner can be selected in the custom column drop-down on the Leads & Accounts page. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.leadboxer.com/leadboxer/account-and-billing/users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.