Context

When adding a machine identity to a project template via the "Assign Existing" flow, the identity dropdown only showed a subset of the organization's identities. The root cause: the component called useSearchOrgIdentityMemberships({ search: {} }) without specifying a limit, so the backend applied its default limit of 50. The FilterableSelect then performed client-side filtering on just those 50 results — meaning any identities outside the first 50 (sorted alphabetically) were invisible regardless of what the user typed.

This was reported by a customer whose taf_* identities were not appearing in the dropdown despite existing in the organization.

Before: Dropdown fetches first 50 identities, filters client-side only. Orgs with >50 identities can't find some of them.

After: Dropdown sends the user's search text to the server as a name: { $contains: ... } filter (debounced at 300ms), matching how the Organization Machine Identities page already works.

Steps to verify the change

1. Set up an organization with more than 50 machine identities
2. Go to Organization Settings → Project Templates → edit a template → Machine Identities section
3. Click "Add Machine Identity" → "Assign Existing"
4. Type a name that matches an identity outside the first 50 alphabetically
5. Verify the identity now appears in the dropdown
6. Select an identity and confirm the modal closes cleanly
7. Reopen the modal and verify the dropdown shows the full unfiltered list (no stale search term)

Important things for reviewers

• knownIdentityNamesRef cache (lines ~130–136): A useRef<Map> is populated via useEffect (triggered when searchedIdentities or orgIdentities change) to cache identity names. This avoids stale names in the table when an identity was found via search but falls outside the name-resolution query's limit. Note: since searchedIdentities and orgIdentities are arrays recreated from .map() on each render, the effect will fire on every render — this is functionally correct but could be optimized with useMemo on those arrays if performance becomes a concern.
• limit: 100 on the name-resolution query: This is an improvement over the implicit 50 default but still won't fully resolve names for orgs with >100 identities in the table view. The ref cache mitigates this. A dedicated batch-lookup-by-ID endpoint would be the ideal long-term solution.
• filterOption={() => true}: Client-side filtering is fully disabled since the server handles search. During the 300ms debounce window after typing, the dropdown briefly shows results from the previous server response.
• Not tested in a live environment — lint and type checks pass. Manual QA with a large identity set is recommended.

Updates since initial revision

• Moved knownIdentityNamesRef population from render-time mutation to a useEffect (per React best practices, raised by Greptile review)
• Added setIdentitySearchInput("") reset in handleAddOrgIdentity and handleCloseAddIdentityModal to prevent stale dropdown results when reopening the modal (raised by Devin Review)

Link to Devin run: https://app.devin.ai/sessions/d1a8cb051f3d43bd943088cbc553e2c2
Requested by: @0xArshdeep

Type

• Fix
• Feature
• Improvement
• Breaking
• Docs
• Chore

Checklist

• Title follows the conventional commit format: type(scope): short description
• Tested locally
• Updated docs (if needed)
• Read the contributing guide