Task and story permissions

Board membership grants read access. Project owners can update, move, claim, and delete any card. Invited members can perform these operations only on cards whose assigneeIds include their authenticated user ID. Bulk deletion rejects the entire request if any selected card is not editable. New tasks and stories that omit assignees default to the authenticated user. Editors preselect that user and preserve an explicit empty selection.

The board GET response includes members, role, and currentUserId in addition to tasks and stories. Native clients preserve assigneeIds through persistence and cloud sync. GET /api/v1/docs/repositories?boardOnly=true returns owned and invited board projects; ordinary document access remains unchanged. Scoped access tokens still require the matching docs scope.

Queued task changes re-check membership and lock the task row while checking assignment before applying the change. Service checks protect story changes, claims, and deletion. Client controls are supplementary; the server authorizes every request.

Invitation links redirect to a public invitation page. A signed-out visitor must sign in to Autopilot; OAuth returns to that invitation before acceptance. Invitations remain subject to the existing expiry, single-use, and invited-email checks.