> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Show CRM fields everywhere, and rename them for partners
> Add any CRM field to Introw's partner, contact, and object lists, edit values inline, and rename fields to partner-friendly labels on partner-facing views.
Introw's views are never limited to Introw's own fields like tier and segment. **Any field that syncs from your CRM - standard or custom - can be shown as a column** wherever a record appears: the partner list, the contact list, and each object's overview. It can also be **edited from Introw**, on the list and on the record itself, writing straight back to the CRM. And on the **partner-facing** views, every field you expose can be **renamed to partner-friendly terminology** - so partners see "Deal stage" as "Where we are", not your internal property name. The value stays live from the CRM; only the label is yours.
## Watch it
## The three moves
On any Introw view, add columns for any synced field from the partner Account/Company, its contacts, deals, or a custom object. No field is off-limits, no re-modelling needed.
Any editable CRM field can be changed inline, wherever it appears: the partner list and a partner's own record, the People list and a contact's own record, and object overviews. The write goes straight to the CRM.
On the partner-facing views (portal pipelines and CRM lists), give each exposed field a display label that fits your partners' language. The original label stays as a tooltip, and the CRM value never changes.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
f["One CRM field
e.g. StageName / dealstage"]
f --> pt["Partner list
shown as a column"]
f --> ov["Deal overview
shown as a column"]
f --> pf["Partner portal list
renamed: Where we are"]
```
Renaming is **display-only relabeling, not data duplication.** You are not creating a new CRM field or copying values - Introw stores a label override for the view and keeps reading the live value from the CRM. Change your mind, change the label; the data is untouched.
## Internal views - add any CRM field
Introw's internal tables let you add any synced CRM field as a column, alongside Introw's own properties.
In the partner list's **configure panel**, use **Add property** to add any built-in or CRM-backed field (account owner, region, health score, renewal date, a custom field), then save it into shared or private views. Full walkthrough: [Organize the partners list](/features/partners/partner-management/guides/organize-the-partners-list).
On a partner's **People** tab, select **Configure → Add property** to add any synced Contact field (job title, seniority, country, a custom field).
### Object overview pages
Every mapped object has a team-side overview at **`/overview/{object}`** - [Deals](https://app.introw.io/overview/DEAL), Contacts, Companies, Tickets, or a custom object. These are full tables of the CRM object: use **Add property** to add any CRM field as a column, save more than one view, and set the filters your team needs.
## Manage CRM fields, don't just display them
Showing a field is half the job. Anywhere a CRM field appears in Introw's internal views, an **editable** field can be changed **inline** and the write goes straight to the CRM. Your team never has to leave the partner record to fix a region, move a lifecycle stage, or set a renewal date.
The columns you configure are the fields you manage, on both the list and the individual record:
| Where | Which fields appear | What you can do |
| ---------------------------------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------------- |
| **Partner list** | The `crm__` columns on the partner overview view | Edit any editable field inline, in the cell |
| **A partner's record** - the **Partner Info** card | The same partner-overview columns, stacked as rows | Edit inline on the record, without opening the list |
| **People list** on a partner | The CRM columns on the people overview view | Edit any editable Contact field inline |
| **A contact's record** - the **{CRM} fields** section on the person's detail | The same people-overview columns | Edit inline, plus an **open in CRM** link to the contact |
| **Object overviews** (`/overview/{object}`) | The columns you configure per object | Edit inline on deals, tickets, companies, custom objects |
Because both record views read the *same* configuration as their list, you set the columns once and they follow you from the table into the record. A field flagged to hide on the card is left off the **Partner Info** card while staying in the table.
**What stays read-only.** Introw only offers an inline editor where the CRM itself allows a write:
read-only properties, owner and other record-reference lookups, and picklists whose options have not
synced are rendered as values, not inputs. You also need write access to Partners, and the record has
to be CRM-backed - a partner or contact that exists only in Introw has nothing to write to.
This is the CRM-native bet in its smallest form. There is no Introw copy of the field to reconcile:
the value you see is the CRM's, and the value you type becomes the CRM's. Your partner team gets a
purpose-built surface, and your CRM admin keeps a single source of truth.
## Partner-facing views - add *and* rename
This is where the field controls matter most, because partners should never meet your internal property names. On a **pipeline view or CRM object list** inside a partner experience you can:
* **Choose which fields partners see and edit** - expose only the properties that make sense for partners.
* **Rename each to a partner-friendly label** - the configurator lets you edit the displayed label per field (the original is kept as a tooltip), so `dealstage` reads as "Stage" or "Where we are".
* **Do the same on partner profile fields** - choose which partner-object fields show on a partner's profile and override each label.
Renaming for partners is the difference between a portal that feels built-for-them and one that leaks your internal jargon. "hs\_deal\_stage" becomes "Stage"; "Partner\_Tier\_\_c" becomes "Your level" - all without touching the CRM. Configure it on the pipeline/CRM list in a partner experience: [Shared pipelines](/features/co-selling/shared-pipelines).
## Custom partner objects work the same way
If you model partners on a **custom object** rather than the standard Account/Company, its fields sync too - so the same **Add property** flows surface your custom object's fields on every view above, and the partner-facing relabeling works identically. Object and field labels sync from the CRM, so Introw already speaks your terminology before you rename anything.
## Verify it worked
Open the partner list (or an object overview): the CRM columns you added appear with live values, and editing an editable one updates the record in your CRM. Open a single partner and the same fields appear on the **Partner Info** card, editable there too; open one of their people and the **{CRM} fields** section shows the contact's columns with the same inline editing and a link through to the contact in your CRM. Change a value in Introw, refresh the record in HubSpot or Salesforce, and the new value is there. In a partner experience's pipeline/CRM list, the fields you exposed show to partners under the partner-friendly names you set, with everything else hidden.
## Related
The full walkthrough for partner-list views, columns, filters, and phases.
Configure the partner-facing pipeline/CRM list: visible, editable, and renamed fields.
Get partners and their contacts (and all their fields) into Introw first.
Link those partners' deals and opportunities back to them.