organization_person:delete

Status: 📅 Planned - Coming Soon

Description

This mutation message will remove the link between a person and an organization. This deletes the collaboration/relationship record without deleting either the person or the organization.

Expected Functionality

When implemented, this mutation will:

  • Remove a person’s association with an organization
  • Delete the collaboration record linking them
  • Return a message_id for async processing
  • Preserve the person and organization records

Expected Request Schema

{
  "payload": {
    "type": "organization_person:delete",
    "organization_id": 123,
    "person_id": 456
  },
  "signature": "payload_ed25519_hex_signature",
  "source_public_key": "your_client_public_key"
}

Request Attributes

  • payload.organization_id - Integer - The organization ID
  • payload.person_id - Integer - The person ID to unlink

Expected Response Schema

{
  "source_public_key": "community_public_key",
  "source_site": {
    "protocol": "https",
    "fqdn": "arkipel.example.com"
  },
  "created_at": "2025-11-13T20:52:49Z",
  "signature": "...",
  "payload": {
    "type": "organization_person:delete",
    "message_id": "abc123def456"
  }
}

Async Processing

This is an asynchronous mutation. Use arkipel_messages:query with the returned message_id to check deletion status.

Timeline

Expected implementation: Q2 2025

Get Notified

Want to know when this feature launches? Contact us at devkit@arkipel.co

Relationship vs. Deletion

It’s important to understand the difference:

Operation Person Record Organization Record Relationship
organization_person:delete Preserved Preserved Deleted
person:delete Deleted Preserved Deleted
organization:delete Preserved Deleted Deleted

Use Cases

  • Role Changes: Person leaves an organization but remains in the community
  • Staff Updates: Remove former employees from organization records
  • Cleanup: Remove incorrect or outdated organization affiliations

Return to API Specifications