For the usage of a platform, approval from each department is required.
[Approval Level] is configured in the selected menu when adding a platform. The approval flow of a platform changes according to [Approval Level].
When [Approval Level] is specified, the approval flow is as described below.
Figure 4.7 The Platform Approval Flow (for Project Users, with the Level Specified)
*1: The approval flow is defined according to the settings performed by the operators. Contact the operators.
*2: The approver is a user who has the approver role of the organization linked with the accounting code added to the project information.
In [Operation] in the diagram above, not only approval, but also rejection and cancellation operations can be performed. For details on operations and statuses of requests, refer to "Figure 5.1 Changes in Request Status".
Figure 4.8 The Platform Approval Flow (for Project Managers, with the Level Specified)
*1: The approval flow is defined according to the settings performed by the operators. Contact the operators.
*2: The approver is a user who has the approver role of the organization linked with the accounting code added to the project information.
In [Operation] in the diagram above, not only approval, but also rejection and cancellation operations can be performed. For details on operations and statuses of requests, refer to "Figure 5.1 Changes in Request Status".
First, approval is granted at the level of the project belonging to the platform. When the user who performs addition, modification, and deletion has the role of project user, approval must be granted by the project manager of the project to which the platform belongs ("Figure 4.7 The Platform Approval Flow (for Project Users, with the Level Specified)").
When the operating user is a project manager, approval is not necessary ("Figure 4.8 The Platform Approval Flow (for Project Managers, with the Level Specified)").
Next, approval is granted by the organization linked with the accounting code of the project. In the project, the accounting code to manage the payment type of usage charges of the platforms under the project is added. This accounting code links the project to a specific organization and approval is granted by this organization. Next, the approval depending on [Approval Level] specified in the menu is granted on each level (such as approval by department or division). When there is no organization linked with an accounting code, approval by the organization is skipped.
Last, approval is granted by the operators. The approval flow of operators is a route configured in the system based on the operation environment.
After approval on all levels, addition, modification, and deletion are reflected.
When "No Approval" is specified for [Approval Level] of the selected menu, the flow is as described below.
Figure 4.9 The Platform Approval Flow (No Approval)
*1: The approval flow is defined according to the settings performed by the operators. Contact the operators.
In [Operation] in the diagram above, not only approval, but also rejection and cancellation operations can be performed. For details on operations related to and statuses of requests, refer to "Figure 5.1 Changes in Request Status".
When [Approval Level] of the menu is "No Approval", approvals at the level of the project to which the user belongs, and at the level of the organization linked with the accounting code, are not necessary.
After approval is granted by the operators, addition, modification, and deletion are reflected.
Information
When addition, modification, and deletion are performed by an administrator user, regardless of the menu settings, addition, modification, and deletion are reflected without the need for approval.
Email Notifications Related to Approvals
After a request is submitted or intermediate approval is granted, a request for approval email is sent to all subsequent approvers in the approval flow.
In addition, a notification email with a copy of the request is sent to the user who performs the operation.
After the final approval is granted, the details of the addition or modification are reflected to the system. Upon reflection, a notification of approval completion email is sent to the requester. When the reflection fails for some reason, an error notification email is sent to the requester (TO) and the request operator (CC).
Confirmation of Request Statuses
To confirm the approval statuses and details of requests for addition, modification, and deletion, view the [Request Management] window.
For details on how to perform the main operations in the [Request Management] window, refer to "Chapter 5 Request Management".
