# How to share-transfer-report to
### Some background
Although ECCAIRS 2 is mainly used to process reports submitted to an Authority, it may sometime be necessary to inform other Authorities, to ask other Authorities to contribute or to pass on a report to another Authority. ECCAIRS2 provide the means to cater for these needs.
ECCAIRS2 introduced three actions:
· Share on Occurrence
· Transfer Full Ownership of an Original Report
· Report an Occurrence to
There is some confusion between the terms “Share”, “Transfer Full Ownership” and “Report to”. It is essential to clarify the distinctions to hold effective communication between parties as misunderstandings caused by this confusion may lead to incorrect processing of reports and occurrences.
### Actions
#### Sharing an Occurrence
Ultimately an Occurrence needs to be shared by the Competent Authority with the European Central Repository (ECR). At the same time E2 provides the means of sharing an Occurrence with other Authorities.
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/w6oimage.png)
This functionality is combined in the make major and share action.
It is possible to directly set the Occurrence in the major version status, share it with the ECR and share it to multiple Authorities at the same time.
At the end of each Occurrence list view row there are three vertical dots.
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/MpHimage.png)
The “include attachments” switch allows for attachments to be shared too.
If the Authority has setup attributes that can be de-identified and the switch is set to de-identify attributes, the user can choose which attributes from the by the Authority predefined list need to be de-identified.
The Authority with whom the Occurrence is shared will no get informed unless it has setup a notification to do so. The shared Occurrence will be accessible to the other Authority via the shared tab and the advanced filters.
#### Transfer full ownership.
Notwithstanding that ECCAIRS2 has put a lot of fail saves in place to prevent reporters submitting reports to the wrong Authority, this sometimes happens. In most cases this happens with unregistered users or registered users not belonging to a registered organisation that must choose to which Competent Authority they have to report to.
In the event an Authority received such an erroneously submitted report, it may decide to contact the reporter if contact details are available or to re-allocate the report directly to the correct Authority. The latter is done via the Transfer ownership.
Via the kebab menu (Three vertical dots) of the erroneous report select Transfer full ownership
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/UXmimage.png)
When the transfer ownership interface appears, the user can choose the correct Competent Authority from the proposed list.
##### [](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/091image.png)
Be aware that this is an irreversible action and cannot be undone.
The report will completely disappear from the Authority’s radar; it will be as it was never received.
The Authority that the report is transferred to, will receive it as an Original Report, it will just have in the version history an indication that it was transferred from.
#### Report To
This action is used when an Occurrence concerns 2 Authorities (e.g., CAA & SIA). It will create 2 separate streams. Both streams can be worked on separately, yet there is only 1 Authority that can share the occurrence with the ECR as competent Authority.
##### Process flow
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/sgnimage.png)
1. A report is Submitted by a reporter to Authority 1. This Authority processes the Original Report up to a Major version of an Occurrence and shares it with the ECR
2. Authority 1 considers that Authority X is to collaborate. Authority 1, Reports the Occurrence to Authority X where it comes in as a new Original Report. As of now there exist 2 separate process flows.
3. Authority X processes the Original Report up to a major version of an Occurrence and then reports the Occurrence back to Authority 1. This receives it as an Original Report and can process it to a Validated Report which is then merged with the existing Occurrence which is then shared again with the ECR.
4. Although there is nothing that prevents Authority X to also share the Occurrence with the ECR. It should refrain from doing so to avoid unnecessary duplicates in the ECR
5. If Authority 1 receives an updated report and processes it up to an OC and if that OC is made major, Authority X will automatically receive a new version of the OR, this without having to share it again
##### Interface
Via then kebab menu (three vertical dots) on the Occurrence list view select “Report to”.
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/WILimage.png)
In the interface, select the Authority to whom the Occurrence is to be reported to
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/yotimage.png)
After the submit, the Occurrence is reported as an Original Report to the addressed Authority. The second flow is established
##### Setup a notification
Via the notification manager a notification can be setup to be informed about a report you received
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/Mhhimage.png)
[](https://help.ci-aviationreporting.eu/uploads/images/gallery/2025-11/7Juimage.png)
1. The name of the notification
2. As an Occurrence (OC) which is sent to your Authority using the “Report To” will create an Original Report (OR), the source needs to be Original Report
3. In which library is the notification to be saved
4. Which query will target the Original Reports
5. On what action is the notification to be triggered (multiple selections are possible)
6. Who will be notified
a. Role à all users having a specific role
b. Targeted individual users
c. Users belong to a group
7. How will the users be notified
a. On their landing page (notifications)
b. Via a email
8. At what frequency will the notifications be sent