> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/platform/settings.md). # Settings How to manage general, team, integrations, and technical settings. Spara's settings page covers general, team, integrations, and technical settings. * **General** * Company description: A brief description for how you want Spara to describe your business. * Sales avatar: The name, title, and profile image of how Spara is represented in all channels. * Cross Channel Opt-Outs: Whether a lead who asks to stop on one channel (email, text, or phone) is opted out of all three. On by default. When off, each opt-out covers only the channel it came from. * **Team** * Invite and manage team members — see [User Management](/platform/settings/user-management.md) * **Chat** — settings for your chat agents, organized into tabs: * **Deployment** — embed code and deployment configuration * **Themes** — visual styling for chat widgets * **Media** — images and media used in chat * **Admin** — response length and other admin-only settings (visible to admins only) * **Email Configuration** — settings that apply across all email activity: * **Daily send limits** — cap on outgoing emails per day * **Email Tracking** — enable or disable open-tracking pixels and link rewriting on outgoing emails. See [Email](/build/channels/email.md) for details. * **Product Demo** — settings for your Product Demo agents, including the Spara Scanner tab * **Integrations** * Connect and configure Spara's native integrations to third party applications. See [Calendar Integrations](/integrations/calendar-integrations.md), [Communications Integrations](/integrations/communications-integrations.md), [CRM Integrations](/integrations/crm-integrations.md), and [Document Sync Integrations](/integrations/document-sync-integrations.md) for more details. --- # 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.spara.com/platform/settings.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.