Role apply on SunfishLoop now auto-opens an approval task

Description and use

Auto-creating an approval task for role applications in SunfishLoop streamlines admin review by consolidating chat, progress, and decision into a single unit.

Problem

Admins lacked a unified collaboration unit for reviewing role applications, requiring separate decision APIs and lacking chat or progress logs.

Outcome

The new auto-created approval task streamlines admin review, consolidating chat, progress, and decision into a single unit without adding a new decision API.

Workflow

• Candidate applies via POST /api/v1/roles/:roleId/applications, receiving auto_accepted:false and a task in the response.
• Admins receive application.submitted notification and open the task brief to review applicant notes, profile, and role link in the task chat.
• Admins use POST /api/v1/applications/:id/decision to accept or reject; accept completes the task and records progress, reject voids the task and records progress. The application closes with the decision.

Evidence

when someone submits POST /api/v1/roles/:roleId/applications, the familiar application.submitted work-notification / webhook still fires — and the server auto-creates a project task titled「{applicant} 申请岗位「{role name}」」, linked by application_id / role_id.

Source

Task members are approval-capable admins only (project owner + 协作管理者, plus role.reviewer_ids when set). The applicant is never a task member, so they cannot self-approve.

Source