How People and Contacts Work

The People page shows everyone connected to your companies — officers, directors, accountants, legal counsel, and so on. One person often works with more than one company, so the same person can show up linked to several of them at once.

Each entity keeps its own copy

Each entity keeps its own copy of these details. Editing one changes that entity only.

If Dana is CFO at three of your companies, Equipath can show her as one linked person so you don't end up with three disconnected entries. Behind the scenes, each company still stores its own copy of her name, email, phone, and address. Editing Dana at Company A never changes Company B or Company C.

That's also why her details don't have to match everywhere. She might use dana@companya.com at one client and a personal cell number at another. Neither is a mistake — it's how a person who serves multiple companies actually operates.

Use Save to [Entity] to write one company's copy. Nothing else moves.

Locked rows (view-only)

A lock on a row means you have view-only access to that entity — nothing there can be changed by you. You can still see the details.

Locked copies stay visible so you can compare them with the ones you can edit. They are never rewritten by your saves.

Apply to all entities I can edit

Apply to all entities I can edit is the opt-in way to copy the details you're looking at onto every linked entity you can edit.

• It writes those details only to entities you can edit.
• You don't have edit access to view-only entities, so those copies are left as-is.
• It never runs on its own. Editing one copy does not change the others unless you click this button.

The caption under the button states the exact scope before it runs — which entities will be written, and which stay unchanged.

Differences

When a linked person's details disagree across entities, Equipath shows a Details differ warning so nothing slips through unnoticed. Open it to compare and reconcile.

Some differences are completely legitimate (different emails on purpose). Some are simply out of date. Equipath can't tell those apart automatically, so it flags them and lets you decide.

You can Accept difference when the values should stay different.

Accepting a difference marks it as OK on every entity you can edit. The warning clears once every entity you can see either has an accepted value or matches one. Entities you can't edit can't be marked directly, but they're covered when their value matches an accepted one.

Once accepted, the row shows Difference accepted instead of going silent — so a reviewed difference is never invisible. If someone later edits a value that was accepted, the warning comes back so you can take another look.

Name, email, phone, and address can all be accepted this way.

Merge — same person, link them

If someone else with this name isn't linked to this record, and they're the same person, merge them.

Merge links the records as one person. Each entity keeps its own contact details and roles — merge never changes stored details. If they disagree, the merged row flags it so you can compare and pick a version afterwards.

You can only merge records on entities you can edit. Copies on entities you don't have edit access to stay separate until someone with access merges them.

Unmerge — not the same person

Use Not the same person? when some of the linked records actually belong to a different person. Pick the entity records that belong to someone else. They'll get their own contact and show up as a separate row — their roles and contact details are left exactly as they are.

Shared email regroups them

People who share an email are grouped together. If you split two records that still share an email, they'd be linked again right away. Give one side its own email first, then split.