Appearance
Interface customization capability map
Use this map to plan the scope of interface customization.
Capability layers
| Layer | Features | Purpose |
|---|---|---|
| Application | Platform applications and CRM application views | Defines the overall work entry point for a role. |
| Navigation | Web and App main navigation | Controls the first application entry points that users see. |
| Menu | CRM menus and custom menu items | Controls object, page, and chart entry points. |
| Page | CRM homepages and Web or App custom pages | Builds workspaces and business pages with components. |
| Component | Common, BI, collaboration, business, and custom components | Provides draggable page content. |
| Brand | Theme Color, Skin Color, startup image, and branding | Controls visual identity. |
Custom Component and Custom Plugin capabilities extend page content and interaction.
Capability-to-source feature mapping
| Source feature | Layer | Recommended scenario |
|---|---|---|
| Platform application | Application | Create an entry point for an independent business team. |
| CRM application view | Application, page, and menu | Configure menus and homepages together in the new CRM. |
| CRM menu | Menu | Provide different Object and feature entry points by role. |
| CRM homepage | Page | Provide role-specific Workstation components. |
| Web main navigation | Navigation | Control Level 1 Web application entry points. |
| App main navigation | Navigation | Control Level 1 Mobile Client entry points. |
| Web Custom Page | Page | Build Web business pages. |
| App Custom Page | Page | Build Mobile Client business pages. |
| H5 page | Page | Connect an existing mobile Web Page. |
| Custom menu item | Menu | Turn Objects, pages, and charts into menu entry points. |
| Theme Color and Skin Color | Brand | Unify the enterprise visual style. |
| App startup image | Brand | Present mobile branding at startup. |
| Component, Custom Component, and Custom Plugin | Component | Extend page Content and interaction. |
Client support
| Capability | Web | App | DingTalk | WeCom | Feishu |
|---|---|---|---|---|---|
| Web main navigation | Support | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| App main navigation | Not Applicable | Support | Support | Support | Support |
| CRM Web view | Support | Adaptive with limits | Depends on integration | Depends on integration | Requires review |
| CRM mobile view | Not Applicable | Support | Support | Support | Requires review |
| Web custom page | Support | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| App custom page | Not Applicable | Support | Support | Support | Requires review |
| H5 page | Not Applicable | Support | Support | Support | Requires review |
NOTE
Feishu support comes from the Applicable Platform field in source materials. Review actual presentation and integration behavior.
Recommended planning order
- Identify user roles and frequent tasks.
- List the applications, objects, pages, and charts that each role needs.
- Design platform applications or CRM application views.
- Configure menus and homepages.
- Configure Web and App main navigation.
- Configure Theme Color, Skin Color, and startup images.
- Let key users test the experience and provide feedback.
Planning checklist
| Check | Description |
|---|---|
| Separate Web and mobile | Each client requires a different navigation and page strategy. |
| Separate Tenant and Personal Level settings | Administrators define defaults; users define preferences. |
| Define Applicable Scope | Prevent irrelevant users from seeing a template. |
| Confirm Template Priority | Define which matching template loads by default. |
| Confirm rollout and pricing | Some App customization and branding features need additional approval. |
| Plan rollback | Record navigation, page, and branding settings before release. |