> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/tenant-settings.md). # Tenant Settings In **Tenant Settings**, admins can manage different aspects of their tenant effectively. They can change the tenant name, activate dark mode for a personalized feel, view and add licenses, set default finding status, configure sub-status options, manage notification and server settings, create email templates, and set up short codes. **Tenant Settings** contains the following sections:


Account Information	manage tenant name, set dark mode, update tenant logo and icons, enter and view licenses	ff.png	Account Information
General Settings	answer types, default findings status, sub-status configuration, rapid templating	ff.png	General Settings
Email Settings	manage notification settings, server settings, email templates	ff.png	Email Settings
Tags Settings	manage the list of tags existing in a tenant	ff.png	Tags Settings
Service-Level Agreements	manage the business rules for SLAs	ff.png	Service-Level Agreements (SLAs)
Short Codes	set up and configure short codes	ff.png	Short Codes

--- # 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.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/tenant-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.