OUT-3975 | Profile Manager App - Company custom fields are showing but tags are not

[arpandhakal]

The main changes are

• filtered custom field to only fetch custom fields related to client, previously company custom fields were also shown which was never intended.

Testing

Company Phone Number is a custom field for company:

IU View (old):

IU View (fixed, filtered custom field for company):

CU View (old):

CU View (fixed, filtered custom field for company):

[linear-code]

OUT-3975

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
client-profile-manager	Ready	Preview, Comment	Jul 14, 2026 11:13am

[priosshrsth]

lgtm

[greptile-apps]

Greptile Summary

This PR restricts profile custom fields to client-scoped definitions. The main changes are:

• Add entityType to the custom-field response schema.
• Filter custom-field results to entityType === 'client'.
• Return an empty array when the API returns no field data.

Confidence Score: 5/5

This looks safe to merge after handling custom-field responses without entityType.

• Client-scoped filtering matches the intended profile behavior.
• A response that omits entityType can fail schema parsing before filtering.

src/types/common.ts

Important Files Changed

Filename	Overview
src/types/common.ts	Requires entityType on every parsed custom-field response.
src/utils/copilotApiUtils.ts	Filters custom fields to client entities before returning them to callers.

_{Reviews (1): Last reviewed commit: "fix(OUT-3975): filtered custom field to ..." | Re-trigger Greptile}

[greptile-apps]

Missing entity type rejects response

When listCustomFields() returns a field without entityType—for example from an older API response—the schema throws before the filter runs. Every getCustomFields() caller then fails instead of returning its custom-field data, so make this field optional or use the response field guaranteed by the API.

[arpandhakal]

I believe the api guarantees the entityType prop @greptile

[greptile-apps]

Fair enough — if the API contract guarantees entityType is always present, then a required field in the schema is the right call. It'll correctly reject any malformed response rather than silently passing through bad data. I'll withdraw the concern.

Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.