> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/organization/company-settings.md). # General Settings **Settings → General Settings** holds your tenant's company profile and the organization-wide defaults that other surfaces inherit. It's the canonical record of who your organization is on PeakCommerce — the name, contact details, and browser-tab branding that show up in portals and pages — plus the fallback timezone applied across the platform. Getting it right here means you don't have to repeat it everywhere else. ## Company Profile * **Tenant ID / Tenant Status** — your tenant's unique identifier and its lifecycle status. Both are read-only; quote the Tenant ID when you contact PeakCommerce support. * **Environment Name / Company Name** — managed by PeakCommerce operations and locked in the UI. These anchor environment-level naming, so reach out to support if either is wrong. * **Tenant Name** — editable. This is the display name shown in your portals by default unless a portal overrides it with its own name. * **Address, City, State/Province, Postal Code, Country, Phone, Website** — your organization's contact details, surfaced where customer-facing pages reference your company. ### Portal Favicon The browser-tab icon for your customer and partner portals. There are two ways to set it — upload a file, or point at an icon you host yourself: * **Upload favicon** — click **Upload favicon** and pick a PNG, JPEG, GIF, WEBP, SVG, or ICO file up to **256 KB**. The file is validated by its actual content, not its filename or declared type — a renamed file won't slip through. SVG favicons must be **passive images**: an SVG containing scripts, inline event handlers, or `javascript:` URLs is rejected outright (with a clear error) rather than silently stripped. Uploading fills the URL field below automatically; **Remove** deletes the uploaded file and reverts your portals to the PeakCommerce icon. * **Portal Favicon URL** — alternatively, paste the URL of a publicly reachable square icon you host elsewhere. Leave both blank to use the PeakCommerce icon. **Where each one applies.** An uploaded favicon is served through the signed-in session, so it appears on **signed-in** customer and partner portal pages. Anonymous public pages (storefronts, signup flows) and the admin/CSR app keep their existing icons — the admin and CSR views always show the PeakCommerce icon. If you need to brand the tab icon on **anonymous** public pages, a publicly hosted **Portal Favicon URL** remains the way to do it. ## Organization Defaults * **Default display timezone** — the timezone applied to users who haven't set a personal preference. Individual user preferences always take priority; leave it unset to fall back to each user's browser timezone. Click **Save Changes** to apply. Next: brand the hostnames your portals serve from under [Domains](/product/settings/organization/domains.md), or return to the [Settings overview](/product/settings/settings-overview.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://docs.peakcommerce.com/product/settings/organization/company-settings.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.