Organization branding and settings

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Update organization branding and settings

Use Settings → Organization Profile and Branding for the organization identity shown in supported interfaces. General, Authentication, Notifications, Network, Billing, Integrations and System contain different operating settings; a branding change should not be used to alter access policy.

1. Confirm the organization whose interface you are editing.
2. Use the release's supported logo/image formats and limits.
3. Review text, colors and readable contrast where configurable.
4. Save and inspect admin and entitled customer surfaces.
5. Test a narrow/mobile layout and sign-in/setup screens where affected.

Use actual business assets rather than a screenshot of the logo. Avoid contact details or links that point to a development tunnel. Refresh/cache behavior can delay visible updates, so verify through a fresh view before submitting repeatedly.

For operational settings, capture the previous value, understand the effect and change one related group at a time. Determine whether a service restart or re-authentication is required. A saved form does not prove the running process has adopted an environment-backed change.

Configuration reference (env vars, ports, URLs) distinguishes deployment environment inputs from database-backed settings. Exact field descriptions and restart requirements must be finalized against the release UI.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.