Add team_assignment_limit_change activity type to OpenAPI spec

[salmanbshah]

Summary

Adds OpenAPI documentation for the team_assignment_limit_change activity type to API version 2.14.

This activity type tracks when team assignment limits are changed by admins, allowing developers to monitor team capacity management changes through the Admin Activity Logs API.

---

Scope

Version: 2.14 only (not in Unstable/unreleased version)

API Endpoint: GET /admins/activity_logs

---

Changes

Activity Type Enum

Adds team_assignment_limit_change to the activity_type enum in the activity_log schema.

Metadata Fields

Adds the following fields to activity_log_metadata:

• team (object, nullable)

  • id (integer): The ID of the team
  • name (string): The name of the team

• team_assignment_limit (integer, nullable)

  • The team assignment limit value
  • null if the limit was removed/unset

---

Example API Response

{
  "type": "admin_activity_log_event",
  "id": "f7bd54f5-3d7e-460b-a5de-9d7ca46c4f51",
  "performed_by": {
    "type": "admin",
    "id": "293",
    "email": "admin@example.com",
    "ip": "172.253.116.141"
  },
  "metadata": {
    "team": {
      "id": 295,
      "name": "Support Team"
    },
    "team_assignment_limit": 10
  },
  "created_at": 1762790574,
  "activity_type": "team_assignment_limit_change",
  "activity_description": "Admin changed team assignment limit to 10 for team Support Team."
}

Unsetting a Limit

When a limit is removed, team_assignment_limit is null:

{
  "metadata": {
    "team": {
      "id": 295,
      "name": "Support Team"
    },
    "team_assignment_limit": null
  },
  "activity_type": "team_assignment_limit_change",
  "activity_description": "Admin unset team assignment limit for team Support Team."
}

---

Pattern Alignment

This follows the established pattern used by similar assignment limit activity types:

• admin_conversation_assignment_limit_change with conversation_assignment_limit field
• admin_ticket_assignment_limit_change with ticket_assignment_limit field

All assignment limit metadata fields store only the current/new value (not old and new), as a single nullable integer.

---

Verification

✅ Tested with API version 2.14:

curl 'http://api.intercom.test/admins/activity_logs' \
  -H 'Intercom-Version: 2.14'

---

Related PRs

Intercom Monolith:

• intercom/intercom#446612 - Updated API presenter implementation (simplified metadata structure)
• intercom/intercom#445742 - Initial API presenter implementation
• intercom/intercom#445704 - Event infrastructure and audit logging

Related Issue:

• intercom/intercom#445916 - Team Data Foundations consultation

---

Review Notes

• This is an additive, non-breaking change
• Only affects version 2.14 (not Unstable)
• Follows existing assignment limit patterns
• API response verified in local testing

[salmanbshah]

Yes, this is for the activity logs endpoint - specifically the activity_log_metadata schema used in the Admin Activity Logs API (/admins/activity_logs).

[salmanbshah]

Fixed! Moved team_assignment_limit_change to the correct alphabetical position in the enum. It's now between security_settings_change and temporary_expectation_change (line 14107) as per the alphabetical ordering of the list.

[junaid-zaidi-intercom]

LGTM!