Release to upstream and downstream organizations (exclusive YIDA)

Exclusive Edition

Ability	Free Edition	Light edition	Professional Edition	Exclusive Edition
Release to downstream organizations	Not supported	Not supported	Not supported	Support

1. Understand what is DingTalk upstream and downstream organizations

Usage scenarios

Scenario

Customer pain points

Business docking between enterprises and internal and external collaboration

To connect with external organizations, you must first find the corresponding docking person. Only after one inquiry, contact information, adding friends, and pulling groups can the work be connected. • No contact for half a month, no reply from the contact person, no answer to the phone; Finally, I contacted and said, "I left..." • To whom the docking person is handed over, another question is asked. • Is the docking person an employee of Company A? The sudden "Flying Order"...... • What level is the docking person? Is it the project person? Can he solve the problem? • What type and level of partners are, and what cooperation policies and standards need to be communicated. Each time, we need to search for partner information data. • For each new supplier, you must send a link to the supplier management system and set permissions. • Where is the process of internal and external collaboration? You need to log on to the system to see that many processes are not supported by the system. The process is not transparent, and the progress is determined by repeated stalking inquiries. • Because communication and cooperation are not timely and broken, the payment is slow, the problem has been checked for a long time, and the business is always delayed.

Solution: upstream and downstream organizations

Main scene: efficient collaboration with partners

• Customer Group Analysis: Enterprises and stable business contacts, especially in the scenario of upstream and downstream industrial chains with enterprises as the core, need to establish a true and credible communication and cooperation carrier.
• Solution: The Enterprise establishes upstream and downstream organizations, invites partners to join, and realizes authentic communication and collaboration in upstream and downstream organizations.

High-frequency business collaboration between organizations

• Mostly used for: upstream and downstream cooperation, such as suppliers, distributors, service providers, external ecological employees, etc.
• Communication and collaboration system of "enterprise-upstream and downstream industrial chain partners" based on Backbone Organizations
• Long-term cooperation and continuous work guarantee

Core Competence

●Upstream and downstream contacts●Upstream and downstream Workbench

Core effect

• Trusted personnel identity-avoid non-active external docking personnel
• Continuous collaboration-the contact person knows at the first time when he leaves, and there is handover at the first time
• Permissions can be isolated-suppliers see supplier-related systems, distributors see distributor-related systems

Enter the application (only available for Certified Enterprises)

The administrator can find the enterprise to be operated in [mobile phone DingTalk] → [address book] → click manage → [Internet platform] → [upstream and downstream organizations]], or find the upstream and downstream organization application directly on the workbench. (How to activate administrator permissions)

Members who have joined the upstream and downstream organizations can enter the organization in [mobile phone DingTalk] → [address book]-[upstream and downstream organizations], or directly find the upstream and downstream organization application on the workbench

2. Publish applications on YIDA to upstream and downstream organizations on DingTalk

Supported version: YIDA exclusive version

Publish the application to the downstream workbench with one click

Applications built by upstream organizations are released to the downstream organization workbench with one click.

Unified upstream management for secure and reliable business

Functions such as business permissions, approval rules, and authorization lists are uniformly managed by upstream organizations to solve the difficulties in organization management and hidden dangers of information leakage of primary enterprises.

1. licence unified management

licence unifiedMain organizationPurchase and distribution.

Supported accountsAutomatic total licence of authorized personnel in the primary and downstream organizations (up to 3) are clear at a glance.

Partner intelligence entry: select a specific department of the downstream organization and automatically authorize the entry. The Liberation administrator will manually manage and maintain it. Partner intelligent resignation: If downstream members leave, Licence will be automatically removed.

2. Share business applications and grasp Business trends

Data changes are visible in real time on the main organization report screen.

Upstream organization: Use the same as common applications. And support the selection of personnel across upstream and downstream organizations. Filter the submitted person and automatically reveal the organization information of the person. View data, data management, ETL, reports, and large screens from an overall perspective.

Downstream organizations: The data management page (running state) is supported. If permissions are granted, you can view the basic details within the scope of permissions (report analysis is not supported in this period). Primary organization Contact: Join the collaborative organization If someone A in the backbone organization needs to cooperate with the personnel of the upstream and downstream organizations, he needs to add A to the upstream and downstream organizations. In the downstream organization, all personnel in the current upstream and downstream organization can be selected when selecting business personnel.

3. Key information, timely reminder

Application release: When the application is published to the downstream, the administrator will be reminded

Account number warning: The downstream organization occupies YIDA Licence of the upstream organization's purchases. When 80% is consumed, a smart reminder is sent to the primary administrator to avoid affecting the usage in the primary organization.

Use Applications downstream, submit data, and participate in approval

Downstream organization workbench and suitable application Workbench

The application center of the downstream organization can see the applications released by the upstream organization. Downstream organizations submit data quickly and participate in approval collaboration

Common FAQ

Q: How to calculate the number of licence people in the main organization and the downstream? Can you give an example?

A: For example, the picture shows licence in the main organization, consuming A total of 2000+200=2200 places and the remaining 800 places. If the downstream organization purchases YIDA independently, it can be used as a standard organization.

Main organization (main organization) Total number: 10000 people in the address book (YIDA exclusive edition of 3000 people) Main organization Workbench: 2000 members in the organization can use YIDA applications

Downstream organization (original cooperation space, first upstream and downstream organization) Total number: 1,000 people (200 people authorized by upstream as partners) Downstream organization Workbench: 200 people can use YIDA from upstream applications

Q: In the application design State of the main organization, can the identity and organization information of the downstream organization be obtained through the formula?

A: Currently, it supports the use of selection components and departments of downstream organizations. PassThe formula is not supported for obtaining information about personnel of downstream organizations (such as DirectBuilder and DeptBuilder).

Q: Is cross-application form scenarios supported

A: Currently, only the business collaboration of the current application is supported. For exampleCross-application scenarios such as data linkage, associated forms, and so on are not supported in upstream and downstream.