Shared contacts
A contact is a reference person of an entity: name, e-mail, telephone and position. It is not a user with access to the platform; it is only the information on whom to contact (see Entities, holders and contacts).
The same contact may be linked to more than one entity at the same time. When this happens, the contact is said to be shared.
Why a contact is shared
It is common and perfectly legitimate. The same person may be the point of contact for several companies, for example:
- a person responsible for the certification of several companies in the same group;
- a firm or consultant representing several clients.
Instead of duplicating the person, the system links the same contact to all those entities. It is the same record: the name, e-mail and telephone are the same for all of them.
The warning on the form
When opening a shared contact for editing, a warning appears at the top of the form:
Warning: this contact is shared by N entities. Any change made here is reflected in all of them.
It serves as a reminder that you are not editing a local copy: you are changing the contact that other entities also use.
You see the number, not the names
The warning indicates how many entities share the contact, but does not reveal which ones. You continue to see
only the entities to which you have access.
What happens when a shared contact is changed
As it is the same record, a change to the data (name, e-mail, telephone or position) is reflected in all the entities that share the contact, at the same time.
From there, the system takes care of notifying the certification bodies involved and of marking the certificates as requiring verification, but only in the certificates where this still makes sense.
Which certificates count
Not all certificates linked to the contact are notified. Only those that are valid and in which the entity is still active count:
- Expired, terminated, suspended or withdrawn certificates are left out.
- Certificates from which the entity has already left as a member or site (it has an exit date) are left out.
In these cases, the change is still recorded in the certificate's activity (for history purposes), but does not generate an e-mail or a verification request: it would make no sense to bother the certification body about a certificate that is no longer active.
To whom, and when
At the moment the change is saved, and only for the certificates that count (text above):
- The certification bodies (CBs) of those certificates are notified, not only those of the certificate in which the editing was taking place. For each certificate, the notice goes to the manager responsible at the CB; if no manager is assigned, it goes to all users of the CB.
- CBs receive the notice by e-mail and in the platform bell. The notification states what changed (the before and after) and who changed it.
- The PEFC Administration always receives a copy by e-mail, just as it does when the data of an entity is changed.
- One notice per certificate is sent: whoever is responsible for several affected certificates receives one e-mail for each.
Holder users never receive these notices, even when they are the ones making the change. It is therefore normal to change a contact and not see any notification on your side: it went to those who need to review it. A CB or the Administration making the change receives the notice like any other recipient.
Who is notified, scenario by scenario
The rule is the same for changes to a shared contact and to the data of an entity (identification, CAE, addresses and associated contacts).
| Scenario | Who is notified | Verification |
|---|---|---|
| The entity is in a single certificate | Nobody. The change is kept in the activity history. | If a Holder made the change, it awaits verification by the CB. |
| The entity is in several certificates and the change is made by the Holder | The CB of each valid certificate where the entity is active, by e-mail and in the bell; the PEFC Administration by e-mail. The Holder receives nothing. | Each of those certificates awaits verification until the CB confirms. |
| The same change is made by a CB | The same recipients, including the CB itself if it is the CB of one of the certificates; the Administration by e-mail. | No verification pending: CB actions are born verified. |
| The same change is made by the PEFC Administration | The CBs of the valid certificates, by e-mail and in the bell; the Administration receives its copy. | No verification pending. |
| Expired, suspended, cancelled, withdrawn or pending certificate, or an entity that has already left (member or site with an exit date) | Nobody, for that certificate. The change is kept in the history. | No verification notice for that certificate. |
| Change to the record of a Certification Body (the CB as an entity) | The certificates that the CB certifies do not count. It only counts if the CB's entity is also a holder, member or site of valid certificates. | As in the scenarios above. |
| Detaching or removing a contact from an entity | Counts as a change to that entity: the CBs of its valid certificates are notified. The other entities sharing the contact are neither affected nor notified. | As a normal change. |
Until 26 August 2026, these notices went to all certificates linked to the entity, even expired ones, and the record of a CB counted as shared by all the certificates it certifies. That is what caused the mass e-mails of July 2026. The rules above have been in force since that date.
What is marked as requiring verification
Each valid affected certificate is marked as requiring verification. The certification body responsible for that certificate sees this status and confirms the change; until then, the change is recorded as pending verification.
This is what ensures that, when a contact person changes in several certificates at once, each certification body has the opportunity to review the change in its own certificate.
An example
Ana is the contact for three companies, each with its own valid certificate, at different certification
bodies. When Ana's e-mail is changed from one of them, all three are
updated, the three certification bodies are notified and the three certificates are marked as
requiring verification. If a fourth company
had an expired certificate, the change would remain in that company's history, but without an e-mail or
verification.
Unlinking is different from changing
Changing data propagates to all. But unlinking a contact from an entity (ending the association) does not affect the others: the association with that entity ends, but the contact and its data remain intact for the remaining ones. As nothing changes for them, this case does not propagate to or notify the other entities.
Contact who is the manager of a certificate
You cannot remove a contact who is the manager of a certificate without first assigning another
manager to that certificate. If that certificate is outside your scope of access, the system
gives a generic warning, without revealing the number of a certificate that does not belong to the user.
Privacy
As with entity sharing, notifications and warnings indicate that a contact is shared, but do not expose the other entities or their data to those who do not have access. You see the number of entities involved, never their identity.