Tabella dei contenuti
Operations and lifecycle
Making availability known
Path: My party → Delegation management → Availability.
The party enables the option to receive delegations for producing and/or consuming.
Availability is disabled by default, and activating it does not imply automatic assignments: each delegation must be evaluated and accepted by the delegate.
Creating and sending a delegation
Path: My party → Delegation management → Delegations granted → Create new.
Steps:
- Select the type of delegation (producing/consuming).
- Select the e-service and the delegated party.
- For producing delegations, if the e-service does not exist, simply enter the name and a short description: it will be created and become delegable.
- The delegating party appoints the delegate as data processor under the GDPR, outside the scope of PDND.
- Send the delegation request to the potential delegate.
Accepting or rejecting a delegation
Path: My party → Delegation management → Delegations received.
The potential delegate reviews the request and can accept or reject it, providing a reason visible to the delegating party.
Operational management (day-by-day)
With an active delegation, the delegate manages the administrative activities of the e-service (producing or consuming) on behalf of the delegating party. For delegated objects, the delegating party cannot perform administrative actions until the delegation is revoked.
Revoking a delegation
Path: My party → Delegation management → Delegations granted → open the record → Revoke.
Effects:
- Producing delegation
- Delegate: loses visibility and operational control over e-services, service requests, and related purposes.
- Delegating party: regains management of e-services and associated objects, which retain their current state (e.g., an “active” service remains “active”).
- Other parties (consumers): no change in access to the e-service.
- Consuming delegation
- Delegate: the service request is archived; purposes are archived and can no longer be used to obtain vouchers; clients remain active but are disassociated from the archived purposes.
- Delegating party: the service request is archived; purposes are archived; clients remain active but disassociated.
States
| State | Description | Allowed actions |
|---|---|---|
| Waiting for approval | Delegation sent by the delegating party; the delegate must review it. | The delegate can accept or reject the delegation (with a reason visible to the delegating party). |
| Active | The delegate manages the e-service on behalf of the delegating party. | The delegating party can revoke it at any time; management returns to the delegating party, preserving the current state of all objects. |
| Rejected | The delegate did not accept the delegation and provided a reason. | The delegating party may propose a new delegation or adjust its terms. |
| Revoked | The delegating party withdraws the previously granted delegation. | Effects as above: for producing (management returns to delegating party, no impact on consumers) / for consuming (service request and purposes archived, clients remain active but disassociated). |
Next page → Delegation for producing
Hai bisogno di aiuto?
Apri un ticket utilizzando l’apposita funzione all’interno della tua Area Riservata
