> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valaclaims.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Relationships

> Link reusable Contacts to a Client and manage the Client's primary point of contact.

## Overview

**Relationships** links reusable Contacts to a Client. Use it to keep the people and organizations involved in a Client's work connected without creating duplicate contact records.

<img src="https://mintcdn.com/vala/Kbb5xaypKnuoA7df/images/client-record/relationships.png?fit=max&auto=format&n=Kbb5xaypKnuoA7df&q=85&s=720dd2851437b41387bb35326fe0deb7" alt="The Relationships tab showing family, provider, and representative Contacts linked to a Client." width="1440" height="900" data-path="images/client-record/relationships.png" />

*Each relationship shows the linked Contact, relationship type, role, and available actions.*

## Add a relationship

<Steps>
  <Step title="Open Relationships">Open the Client record and select <strong>Relationships</strong>.</Step>
  <Step title="Look for an existing Contact">Search for the person or organization before creating another Contact.</Step>
  <Step title="Create a Contact only when needed">If no reusable Contact exists, create an individual or organization from the relationship workflow.</Step>
  <Step title="Describe the connection">Select a relationship type, add the role and notes that help your team understand the connection, then save.</Step>
</Steps>

Useful relationship types include family members such as a spouse or caregiver, a provider, employer, representative, VSO, claims agent, witness, agency, or VA facility.

Use **Archive** when a relationship should no longer be active on the Client record. Archiving a relationship helps preserve the Client's history while keeping current work clear.

## Primary point of contact

One related Contact can be saved as the **Primary POC**. Use **Set as POC** to select it, or **Remove POC** to return to the Client's own contact information.

Where supported, a saved Primary POC can supply contact-mapped form fields and the Client-side e-sign recipient. The Client's identity information remains the Client's. When you send a form for signature, you can choose or override the POC for that send without changing the saved Primary POC. With no saved Primary POC, the Client's own contact information is used. Selecting <strong>Client (self)</strong> uses the Client's own information for that Client-side contact and signing role.

## Portal access

Eligible related Contacts can be invited to scoped Client portal access. An email address is required. When available, choose only the access areas the Contact needs: **Messages**, **Documents**, and **Signatures**. Staff can revoke access or send a new invitation when needed.

## Family information

Saving supported spouse or child information in **Details** can create or update the corresponding Relationship. Changes made directly in Relationships do not automatically rewrite the original family fields in Details. Review both places when updating family information.

## Best practices

* Search before creating a Contact to reduce duplicates.
* Keep relationship types, roles, and notes factual and useful to the team.
* Confirm the Primary POC and portal access scope before sending a form, signature request, or invitation.

## Related workflows

<CardGroup cols={2}>
  <Card title="Details" icon="user-pen" href="/veteran-records/client-details">Maintain Client information and family details.</Card>
  <Card title="Forms & vSign" icon="signature" href="/core-workflows/forms-and-vsign">Choose and verify signers for form workflows.</Card>
</CardGroup>
