Skip to content

Integration of a functionality to enable forwarding of reports from the secondary tenant to root tenant #4457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
evilaliv3 opened this issue Apr 1, 2025 · 1 comment

Comments

@evilaliv3
Copy link
Member

Proposal

Following the development of feature #4330 this ticket is to implement similar functionality in the opposite direction (input).

The idea behind this functionality is to make it possible for an external organization already accrediotated to the system to insert into the system visible both on the secondary and root tenant.

This implementation is intended to be used to enable the organization to forward a report they had received and intended to be accessed by the recipient of the root tenant.

Following the implementation:

  • a user (recipient) of the secondary tenant should be able to insert a report into the system desalinating it to recipients
  • the recipient of the secondary tenant should receive a temporary receipt to be provided to whistleblowers; Whistleblowers accessing with this receipt should be able to see the loaded information and exchange messages with the recipients of the root tenant.
  • the recipient of the secondary tenant by accessing should be able to eventually exchange comments with the recipients of the root tenant but should not be able to see the comments exchanged between the whistleblower and the recipients of the root tenant.
@evilaliv3
Copy link
Member Author

@susannaferro @AnXh3L0 @elbill @larrykind: This is one of the links we discussed today. Please feel free to load here you comments or notes if any.

\cc @giorgiofraschini

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant