DevPortalPagoPA



Tabella dei contenuti

Delegation for consuming

Definition and scope

The delegation for consuming allows a party (delegating party) to entrust another party (delegate) with the administrative management of the consumption of an e-service. The delegation concerns administrative activities only and does not change the ownership of the service request, which remains with the delegating party.
Within the AgID Guidelines on the technological infrastructure of the National Digital Data Platform (PDND) issued by AgID, this functionality is referred to as the “Consumer’s Delegate.”
Delegation for consuming is possible only if the producer has explicitly indicated, in the configuration of its e-service, that consumption by delegation is authorized. This information is visible within the e-service page.

Delegate’s responsibilities

In a delegation for consuming, the delegate:
  • submits and manages the service request on behalf of the delegating party;
  • submits and manages the purposes and the related risk analyses for the service request;
  • may associate clients with the purposes they created only if the producer explicitly allows it.

Operational management

Managing the service request
The delegate manages the service request of the delegated e-service. They can:
  • declare declared attributes and upload documentation to support the verification of verified attributes on behalf of the delegating party;
  • submit, suspend, reactivate, or archive the service request.
Managing purposes
The delegate manages the purposes linked to the delegated service request. They can:
  • complete the risk analyses;
  • select the API calls/day plan;
  • submit, suspend, reactivate, or archive the purposes.
Managing clients and data access
The delegate may associate clients with the purposes they created only if the producer has authorized data access by delegation. To verify this, simply consult the e-service page.

Delegating party’s responsibilities

Visibility and operational scope

The delegating party retains full visibility over:
  • the service request managed by the delegate;
  • the purposes created by the delegate.
They cannot operate on these components, except for the ability to associate their own clients with the purposes created by the delegate within the scope of the granted delegation.

Managing purposes

The delegating party may independently create and manage its own purposes, even when a delegation is in place. The purposes created by the delegating party:
  • are not visible to the delegate;
  • can be activated, suspended, or archived independently.

Managing clients and data access

The delegating party can always:
  • associate its own clients with the purposes created by the delegate;
  • associate its own clients with the purposes created independently.

Hai bisogno di aiuto?

Apri un ticket utilizzando l’apposita funzione all’interno della tua Area Riservata

Dicci cosa ne pensi

Per segnalare problemi o dare feedback, puoi aprire una segnalazione su Github