> ## Documentation Index > Fetch the complete documentation index at: https://api-docs.helpyousponsor.com/llms.txt > Use this file to discover all available pages before exploring further. # Assign relationship managers to selected donors > Updates explicit active donors or all matching records. Explicit cross-organization/unavailable IDs reject the request. All-results mode requires an authorized form context and resolves saved/search/date filters; unresolved search fails safely. Household scope requires every selected donor to have a household and updates each household once after checking all active member forms. Returns the selected donor count, including unchanged assignments. Material plan impact requires a confirmed token before this atomic mutation. ## OpenAPI ````yaml patch /admin/donors/assignment openapi: 3.0.0 info: title: Gratona API description: >- REST API for the Gratona fundraising platform, including donor, donation, sponsorship, program, event, and integration workflows. Endpoints are organized by tag. Most endpoints require either a Passport bearer token or an issued API key — see the Security Schemes section. contact: name: Gratona Engineering url: https://gratona.com email: devs@gratona.com version: 1.0.0 servers: - url: https://api.gratona.com/v1 description: Server Version 1.0.0 security: [] tags: - name: Auth description: >- Login, signup, logout, password reset, and email verification for admin users and donors. - name: Donors description: >- Donor records: CRUD, profile fields, household linkage, search, filters, merge, and duplicate detection. - name: Donations description: >- Individual donation records, recurring commitments, soft credits, refunds, designations, and exports. - name: Sponsorships description: >- Donor-to-entity commitment relationships, lifecycle transitions, and commitment-specific filters. - name: Entities description: >- Recipient records (children, families, projects, animals, etc.), their status, and entity-level fields. - name: Programs description: >- Program / campaign configuration: hierarchy, settings, and program-level metadata. - name: Forms description: >- Custom form builder (HysForm), form fields, standardized donor fields, and field migrations. - name: Trips description: >- Mission-trip management: trips, participants, budgets, tasks, e-signatures, fundraising milestones, and background checks. - name: Communications description: >- Email templates, SMS, newsletters, donor email manager, and per-donor notes. - name: Payments description: >- Payment-gateway management (Stripe, PayPal, Flutterwave, QuickBooks). Excludes inbound webhooks — see the Webhooks tag. - name: Reports description: Dashboards, analytics, scheduled reports, and exports. - name: Admin description: >- Client-account administration: users, groups/permissions, settings, integrations, and account lifecycle. - name: Donor Portal description: >- Endpoints consumed by the donor-facing portal (donor login, dashboard, donation history, messages). - name: Recipient Portal description: Endpoints consumed by the recipient-facing portal. - name: Public description: >- Unauthenticated public endpoints: donor signup, public trip pages, peer-to-peer campaigns, public checkout. - name: Webhooks description: >- Inbound webhooks from third parties (Stripe, PayPal, Flutterwave, Checkr, DropboxSign). Annotated minimally for reference; payload shapes are owned by the upstream provider. - name: Events description: >- Event setup, invitations, registration, ticketing, attendance and event reporting. - name: Journeys description: >- Journey graphs, activation, enrollment, message templates and event follow-up automations. - name: Tasks description: Workspace tasks, assignments, saved task views and record collaboration. - name: Fundraising description: >- Fundraising portfolios, stewardship plans, giving anniversaries and personal donor follow-up. - name: Impact Stories description: Story intake, review, assets, consent and publication workflows. - name: Integrations description: Workspace integration connections, mappings, synchronization and recovery. - name: Email Calendar description: Connected email/calendar accounts and donor interactions. - name: Spaces description: Workspace Spaces and collaborative Pages. - name: Library description: Workspace documents, source connections, files and analysis. - name: Intelligence description: Donor intelligence and Tali workspace workflows. - name: Automation description: >- V3 automation primitive discovery, input validation, invocation and Zapier contracts. - name: Schema description: V3 model, enum, capability and scope discovery. - name: Zapier description: Zapier automation connections, polling feeds and actions. - name: Files description: Files - name: Client description: Client - name: Payment Gateways description: Payment Gateways - name: Email Settings description: Email Settings - name: Admin Dashboard description: Admin Dashboard - name: Recipients description: Recipients - name: Historical Archived Updates description: Historical Archived Updates - name: Team & access description: Team & access - name: Settings description: Settings - name: Notifications description: Notifications - name: Participation description: Participation - name: Users description: Users - name: Wrapped description: Wrapped - name: Donor SignUp description: Donor SignUp - name: Frontend description: Frontend - name: User description: User - name: Workspace description: Workspace paths: /admin/donors/assignment: patch: tags: - Donors summary: Assign relationship managers to selected donors description: >- Updates explicit active donors or all matching records. Explicit cross-organization/unavailable IDs reject the request. All-results mode requires an authorized form context and resolves saved/search/date filters; unresolved search fails safely. Household scope requires every selected donor to have a household and updates each household once after checking all active member forms. Returns the selected donor count, including unchanged assignments. Material plan impact requires a confirmed token before this atomic mutation. operationId: DonorAssignmentController_bulkUpdate requestBody: required: true content: application/json: schema: required: - donor_ids properties: relationship_manager_user_id: description: >- Eligible staff manager; null or omitted clears direct assignment. This key takes precedence over its compatibility alias. type: integer example: 42 nullable: true assigned_fundraiser_user_id: description: Compatibility alias for relationship_manager_user_id. type: integer example: 42 nullable: true scope: description: Assignment target; default donor. type: string enum: - donor - household - null example: donor nullable: true source: description: >- Audit source; defaults donor_profile for single or donor_list_bulk for bulk. type: string maxLength: 128 example: donor_profile nullable: true plan_impact_version: description: >- Signed five-minute token from a 409 impact response, required when open plans are materially affected. type: string maxLength: 4096 example: issued-plan-impact-version nullable: true plan_repairs: type: array items: required: - plan_id - action properties: plan_id: description: Plan ID. type: integer minimum: 1 example: 42 action: description: >- Chosen repair from the impact required_repairs choices. type: string maxLength: 64 example: archive_plan action_donor_id: description: Replacement action donor when required. type: integer example: 42 nullable: true reason: description: Nonblank reason required to archive a plan. type: string maxLength: 1000 example: Preserving the surviving donor plan. nullable: true type: object maxItems: 50 nullable: true donor_ids: description: Distinct active donor IDs or the literal all. oneOf: - type: array items: description: Donor ID. type: integer minimum: 1 example: 42 - description: All matching donors. type: string enum: - all example: all hysform_id: description: >- Required for donor_ids=all: valid organization donor form ID or all. example: all hysformId: description: Compatibility alias for hysform_id. example: all selection: description: >- All-results filter context; explicit ID selections ignore worksheet filters. properties: hysform_id: description: >- Required for donor_ids=all: valid organization donor form ID or all. example: all hysformId: description: Compatibility alias for hysform_id. example: all filterGroups: type: array items: description: Donor worksheet filter group. type: object additionalProperties: true filter_groups: type: array items: description: Compatibility filter group. type: object additionalProperties: true savedFilterId: description: Organization saved donor filter. type: integer example: 42 nullable: true saved_filter_id: description: Compatibility saved filter ID. type: integer example: 42 nullable: true query: description: Search text. type: string example: Jane keysArray: type: array items: description: Search field key. type: string example: email keys_array: type: array items: description: Compatibility search key. type: string example: email date_from: description: Optional creation date range start, used with date_to. type: string format: date example: '2026-01-01' date_to: description: Creation date range end. type: string format: date example: '2026-12-31' type: object nullable: true additionalProperties: true type: object responses: '200': description: Assign relationship managers to selected donors completed. content: application/json: schema: properties: data: properties: updated_count: description: Selected donor count. type: integer example: 42 failed_count: description: Always zero after successful atomic mutation. type: integer example: 0 failures: type: array items: type: string maxItems: 0 scope: description: Applied scope. type: string enum: - donor - household example: donor warnings: type: array items: properties: code: description: Projection recovery warning code. type: string example: PLAN_PROJECTION_RECOVERY_REQUIRED message: description: Warning message. type: string example: >- Assignment saved; plan projection recovery is queued. type: object type: object type: object '401': description: Authentication is required. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Insufficient permission or feature access. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: >- Bulk stewardship authority impact needs confirmation or became stale. content: application/json: schema: required: - status - code - message - data properties: status: description: Error status. type: string example: error code: description: Machine-readable plan conflict. type: string example: PLAN_IMPACT_CONFIRMATION_REQUIRED message: description: Review prompt. type: string example: Review the assignment impact before saving. data: $ref: '#/components/schemas/CrmApiAssignmentPlanImpact' type: object '422': description: Invalid selection, unavailable filter, manager or household scope. content: application/json: schema: $ref: '#/components/schemas/RequestRejection' security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: ErrorResponse: title: ErrorResponse description: >- Generic error envelope used by most controllers. Most error responses pair a human-readable `message` with `status: error`. Some endpoints additionally include `errors` (validator errors), `error` (legacy single-error string), `code`, or domain-specific context fields. required: - message properties: message: description: Human-readable error message. type: string example: Something went wrong. Please try again. status: description: >- Always the literal string `error` for failures. Some endpoints omit this field. type: string example: error error: description: Legacy single error code/string used by older endpoints. type: string example: invalid_request nullable: true code: description: >- Optional application-level error code (not all endpoints populate this). type: string example: DONOR_NOT_FOUND nullable: true type: object CrmApiAssignmentPlanImpact: properties: material_impact: description: Assignment would change authority of open stewardship plans. type: boolean example: false affected_plans: type: array items: $ref: '#/components/schemas/StewardshipPlanImpactHeader' group_plans: type: array items: $ref: '#/components/schemas/StewardshipPlanImpactHeader' maxItems: 0 transfer_candidates: type: array items: type: string maxItems: 0 scope_changes: type: array items: type: string maxItems: 0 eligible_action_donor_ids: type: array items: description: No action-contact changes for assignment. type: integer example: 42 maxItems: 0 collisions: type: array items: type: string maxItems: 0 authority_changes: type: array items: properties: subject_type: description: Assignment subject. type: string enum: - donor - household example: donor subject_id: description: Assignment subject ID. type: integer example: 42 previous_manager_user_id: description: Previous manager. type: integer example: 42 nullable: true next_manager_user_id: description: Requested manager. type: integer example: 42 nullable: true owner_review_required: description: Plan authority review is required. type: boolean example: false type: object required_repairs: type: array items: type: string maxItems: 0 command: description: Signed command type. type: string enum: - subject_assignment - bulk_subject_assignment example: subject_assignment expires_at: description: Impact confirmation expires after five minutes. type: string format: date-time example: '2026-10-20T12:00:00Z' nullable: true impact_version: description: >- Signed actor/organization/command/impact confirmation; resubmit as plan_impact_version. type: string example: issued-plan-impact-version type: object RequestRejection: description: >- Request or workflow rejection. Framework field-validation failures contain errors; semantic rejections may contain message without errors; legacy/provider failures may use error and error_code. The operation description identifies the rejected condition. Domain responses may add current revision, limits or other conflict context. anyOf: - $ref: '#/components/schemas/ValidationErrorResponse' - $ref: '#/components/schemas/ErrorResponse' - required: - error properties: error: description: Legacy or provider-facing error message. type: string example: The request could not be completed. error_code: description: Stable domain error code, when provided. type: string example: WORKFLOW_UNAVAILABLE type: object StewardshipPlanImpactHeader: properties: id: description: Record identifier in this organization. type: integer example: 42 nullable: false subject: properties: type: type: string enum: - donor - household - relationship_group example: donor id: description: Record identifier in this organization. type: integer example: 42 nullable: false type: object stage: type: string enum: - qualifying - managed example: qualifying status: type: string enum: - draft - active - paused - completed - archived example: draft period: properties: start: description: Calendar date. type: string format: date example: '2026-10-20' nullable: true end: description: Calendar date. type: string format: date example: '2026-10-20' nullable: true type: object version: description: Optimistic concurrency version. type: integer example: 2 nullable: false action_donor_id: description: Record identifier in this organization. type: integer example: 42 nullable: true scope_version: description: Count. type: integer example: 2 nullable: false type: object ValidationErrorResponse: title: ValidationErrorResponse description: >- Returned with HTTP 422 when `Validator::make($data, $rules)` fails. The `errors` map is keyed by the failing field name; each value is an array of human-readable error messages for that field. Most controllers also include a top-level `status: error`. required: - errors properties: errors: description: >- Map of field name to array of validator error messages. Example: `{email: [The email field is required.], amount: [The amount must be a number.]}`. type: object additionalProperties: type: array items: type: string status: description: Always the literal string `error`. type: string example: error message: description: >- Optional summary message — present on some endpoints, absent on others. type: string example: The given data was invalid. nullable: true type: object securitySchemes: bearerAuth: type: http description: Passport bearer token authentication for legacy admin sessions. scheme: bearer bearerFormat: JWT apiKeyAuth: type: apiKey description: Gratona API key sent with the compatibility header X-HYS-API-Key. name: X-HYS-API-Key in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.