---
schema_version: "1"
id: 58c7104685eb31e82d38aa5522d9dee60000875eecdddb77e581931d0296d550
title: How Proxy Identity is Resolved For Delegated Access
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/ec_proxy_identity_resolution.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.ec_proxy_identity_resolution.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 34e2e1b955c72a431a27b757d6ade2bde78e0ea7af56ddb8b391db4f268133b2
description: When a student names a proxy, the proxy's first name, last name, and email address are matched with an existing contact and user record. If a contact record exists for the proxy, Salesforce uses the information. If no contact record exists, Salesforce sends a sign-up email. If Salesforce finds a user record for the proxy but no contact record exists, Salesforce sends a sign-up email to invite the proxy to create an Experience Cloud person account.
products:
  - Education
release: "264"
---
# How Proxy Identity is Resolved For Delegated Access

When a student names a proxy, the proxy's first name, last name, and email address are matched with an existing contact and user record. If a contact record exists for the proxy, Salesforce uses the information. If no contact record exists, Salesforce sends a sign-up email. If Salesforce finds a user record for the proxy but no contact record exists, Salesforce sends a sign-up email to invite the proxy to create an Experience Cloud person account.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="Required Editions"><caption>Required Editions</caption> <colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Education Cloud</td></tr></tbody></table>

This decision matrix describes the matching logic and subsequent actions:

| Contact | User | Contact-Contact Relationship | Action |
| --- | --- | --- | --- |
| Yes | Yes | Yes | The student is all set to delegate access. If a contact maps to multiple user records, Salesforce sets the access delegation request status to In Review so that the correct contact can be identified. |
| Yes | Yes | No | Create the contact contact relationship, and then share. Because the contact and portal user record already exist, Salesforce doesn't send a sign-up email. |
| Yes | No | Yes | Create the portal user, and then share. Because the contact is known, Salesforce provisions the portal user. To add information on the profile to be associated when a user is created and other details, update the Create Delegated User and Contact-Contact Relation flow. |
| Yes | No | No | Create the portal user and contact contact relationship, and then share. Because the contact is found, the system creates the remaining records. To add information on the profile to be associated when a user is created and other details, update the Create Delegated User and Contact-Contact Relation flow. |
| No | Yes | No | Send the sign-up email. The existing user record is likely an Education Cloud user. Because the proxy requires an Experience Cloud person account, Salesforce sends an invitation to sign up. |
| No | No | No | Send the sign-up email. Because no contact or user record exists, Salesforce invites the proxy to self-register on the portal. |
| No | Yes | Yes | A contact-contact relationship can’t exist without a contact. |
| No | No | Yes | A contact-contact relationship can’t exist without a contact. |