> ## Documentation Index > Fetch the complete documentation index at: https://docs.azalt.co/llms.txt > Use this file to discover all available pages before exploring further. # Bulk approve, reject, or revert form element submissions > Bulk approve, reject, or revert all form element submissions for a specific form element within a form submission (site + year scope). **Workflow Actions**: - `approve`: Sets all eligible submissions status to "APPROVED" - `reject`: Sets all eligible submissions status to "REJECTED" - `revert`: Sets all eligible submissions status back to "COMPLETED" (pending approval) **Scope**: Only affects submissions for the specified form element within the current form submission (site + year combination). **Permission Requirements**: - User must have APPROVER, MANAGER, or OWNER role in the organization - User must have access to the site where the form is deployed - The form element must belong to the user's organization **Parameters**: - `formElementId`: The unique identifier of the form element - `formSubmissionId`: The unique identifier of the form submission (scopes to specific site + year) - `action`: One of "approve", "reject", or "revert" - `reason`: Optional reason for the bulk approval/rejection/revert action **Eligible Submissions**: - For "approve": Only COMPLETED or REJECTED submissions will be approved - For "reject": Only COMPLETED or APPROVED submissions will be rejected - For "revert": Only APPROVED or REJECTED submissions will be reverted to COMPLETED This endpoint is ideal for workflow management when you need to approve/reject/revert multiple period submissions (monthly, quarterly) for a form element at once. ## OpenAPI ````yaml https://app.azalt.co/api/v1/openapi.json patch /form-element-submissions/{formElementId}/bulk openapi: 3.0.3 info: title: Erguvan Public API version: 1.0.0 servers: - url: https://app.azalt.co/api/v1 security: [] paths: /form-element-submissions/{formElementId}/bulk: patch: tags: - FormElementSubmission summary: Bulk approve, reject, or revert form element submissions description: >- Bulk approve, reject, or revert all form element submissions for a specific form element within a form submission (site + year scope). **Workflow Actions**: - `approve`: Sets all eligible submissions status to "APPROVED" - `reject`: Sets all eligible submissions status to "REJECTED" - `revert`: Sets all eligible submissions status back to "COMPLETED" (pending approval) **Scope**: Only affects submissions for the specified form element within the current form submission (site + year combination). **Permission Requirements**: - User must have APPROVER, MANAGER, or OWNER role in the organization - User must have access to the site where the form is deployed - The form element must belong to the user's organization **Parameters**: - `formElementId`: The unique identifier of the form element - `formSubmissionId`: The unique identifier of the form submission (scopes to specific site + year) - `action`: One of "approve", "reject", or "revert" - `reason`: Optional reason for the bulk approval/rejection/revert action **Eligible Submissions**: - For "approve": Only COMPLETED or REJECTED submissions will be approved - For "reject": Only COMPLETED or APPROVED submissions will be rejected - For "revert": Only APPROVED or REJECTED submissions will be reverted to COMPLETED This endpoint is ideal for workflow management when you need to approve/reject/revert multiple period submissions (monthly, quarterly) for a form element at once. operationId: bulkApproveRejectFormElementSubmissions parameters: - in: path name: formElementId schema: type: string required: true requestBody: required: true content: application/json: schema: type: object properties: formSubmissionId: type: string action: type: string enum: - approve - reject - revert reason: type: string required: - formSubmissionId - action responses: '200': description: Successful response content: application/json: schema: type: object properties: success: type: boolean message: type: string processedCount: type: number updatedSubmissions: type: array items: type: object properties: id: type: string formElementId: type: string periodUnit: type: number newStatus: type: string enum: - COMPLETED - APPROVED - REJECTED required: - id - formElementId - periodUnit - newStatus required: - success - message - processedCount - updatedSubmissions '400': description: Invalid input data content: application/json: schema: $ref: '#/components/schemas/error.BAD_REQUEST' '401': description: Authorization not provided content: application/json: schema: $ref: '#/components/schemas/error.UNAUTHORIZED' '403': description: Insufficient access content: application/json: schema: $ref: '#/components/schemas/error.FORBIDDEN' '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/error.NOT_FOUND' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/error.INTERNAL_SERVER_ERROR' security: - Authorization: [] components: schemas: error.BAD_REQUEST: type: object properties: message: type: string description: The error message example: Invalid input data code: type: string description: The error code example: BAD_REQUEST issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Invalid input data error (400) description: The error information example: code: BAD_REQUEST message: Invalid input data issues: [] error.UNAUTHORIZED: type: object properties: message: type: string description: The error message example: Authorization not provided code: type: string description: The error code example: UNAUTHORIZED issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Authorization not provided error (401) description: The error information example: code: UNAUTHORIZED message: Authorization not provided issues: [] error.FORBIDDEN: type: object properties: message: type: string description: The error message example: Insufficient access code: type: string description: The error code example: FORBIDDEN issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Insufficient access error (403) description: The error information example: code: FORBIDDEN message: Insufficient access issues: [] error.NOT_FOUND: type: object properties: message: type: string description: The error message example: Not found code: type: string description: The error code example: NOT_FOUND issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Not found error (404) description: The error information example: code: NOT_FOUND message: Not found issues: [] error.INTERNAL_SERVER_ERROR: type: object properties: message: type: string description: The error message example: Internal server error code: type: string description: The error code example: INTERNAL_SERVER_ERROR issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Internal server error error (500) description: The error information example: code: INTERNAL_SERVER_ERROR message: Internal server error issues: [] securitySchemes: Authorization: type: http scheme: bearer ````