Pending sync force flush, assignment category updates, and docs clarifications

Over the past week we've shipped district-side pending sync review and force flush, assignment category updates on PATCH, SSO autofill that leaves an existing redirect URI alone, Meta v2 integration-create parity for default transformations and onboarding completion, and several documentation clarifications.

API Updates

• Assignments: Graph and User (/my) assignment PATCH can update category_id.
• Integrations: Creating an integration via the Meta v2 API applies the application's default transformations at create time (same behavior as v1). Developer-owned onboarding invites are marked completed and linked to the new integration in the same create transaction so clients polling the onboarding see the edge.
• SSO: Autofill no longer overwrites an application redirect URI that is already set on the SSO request.

Dashboard Updates

• Pending syncs: District team members can open a pending sync, review staged totals (creations, updates, deletions), force flush when the deletions look right, or cancel the sync. Force flush asks for confirmation when more than 80% of a data type would be deleted. See Reviewing a Pending Sync and Pending Syncs.
• API Logs: Succeeded and failed status presets filter by inclusive HTTP ranges (200–299 and 400–599) instead of a fixed list of status codes.
• Sharing rules: Docs clarify that separate rules combine with OR and conditions within a single rule combine with AND. See How multiple rules combine.
• Sources: Docs for reconnecting as a new administrator stress staying on the existing district team (invite → accept → reconnect) and warn against starting a new connection from the original integration link. See Reconnecting an Admin Account.

Pipeline Updates

• ManageBac: Connecting docs list the API permissions validation and sync require (Students, Teachers, Classes, and School read scopes) and recommend ManageBac's Read-only preset. See Connecting ManageBac.