Appearance
Core interface customization concepts
These concepts determine how interface configurations apply to users.
Concepts
| Term | Definition | Consideration |
|---|---|---|
| Applicable Scope | Controls which users, departments, user groups, or roles can see a configuration. | A user outside the scope cannot see the template. |
| Template Priority | Determines the default order when multiple templates match. | A larger number has higher priority. |
| Tenant configuration | Enterprise interface settings maintained by an administrator in Setup. | Applicable Scope determines its effect. |
| Personal Level configuration | Interface settings maintained by a user. | It affects only the current user. |
| Main navigation | The system's Level 1 application entry points. | Configure Web and App navigation separately. |
| Bottom navigation | Level 1 navigation at the bottom of the App. | You can configure up to five modules. |
| Application view | A combination of pages and menus in an application. | A CRM application view can contain menus and a homepage. |
| Page layout | The region structure for page components. | Web and Mobile Client layouts provide different capabilities. |
| Component | A draggable content unit on a page. | Types include common, BI, collaboration, business, external, and custom components. |
| Theme Color | The primary color for buttons, tabs, switches, and other controls. | Use a preset or custom color. |
| Skin Color | The color of specific regions, such as Web navigation and the mobile top bar. | Maintain readable text and icons. |
Effective priority
Personal Level configuration usually takes precedence over Tenant configuration. If a user's menu, homepage, or navigation differs from Setup, check for personal changes first.
Version differences
The new CRM supports views inside the CRM application. Earlier versions usually configure CRM menus and homepages separately. Legacy H5 pages, WeCom, DingTalk, and HarmonyOS require additional compatibility review.