> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhello/administration/manage-assistants.md). # Manage Assistants Manage Assistants gives SuperAdmins and OrgAdmins a platform-wide view of all assistants with full CRUD operations. ### Edit Assistant Modal Fields


Field	Description	Notes
Assistant Name	Display name shown in the assistant library.	Must be unique within the team.
Category	Groups the assistant in the library tabs (Analytics, Sales, CX, etc.).	Affects discoverability.
Description	Short summary shown on the assistant card.	Keep concise.
Instructions	Full system prompt governing behavior, role, tone, and rules.	Most impactful field. Changes take effect immediately.
Model	The LLM model used (e.g. gpt-4o, gpt-4-turbo).	Available models depend on org configuration.
Created By	Read-only: who originally created the assistant.	Cannot be changed.
Owners	Assign users as owners. Owners can edit and manage the assistant.	Search by name or email. Multiple owners allowed.
Shared With	Visibility: Private, Share with Team, or Share with Anyone.	Changing to Private immediately hides it from non-owners.
Featured	Toggle the star to feature/unfeature in the library's Featured tab.	Use sparingly — Featured section should remain curated.
Enable PII Redaction	Toggle PII redaction on this assistant's model calls.	On by default. Only disable with appropriate authorization.

--- # 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://docs.ixhello.com/ixhello/administration/manage-assistants.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.