Tabella dei contenuti
First access and initial configuration
Once the subscription is completed, the administrators appointed by the Legal Representative can access the platform and begin configuring it. This chapter outlines the key steps to become fully operational.
Access to the front office
To access the PDND front office, follow these steps:
- Login – Access the platform’s Members Area and authenticate using your SPID or CIE digital identity.
- Select party – If you are associated with multiple parties, select the one you wish to operate for.
- Select product – From the list of available products, choose “Interoperabilità.”
- Select environment – Choose the desired working environment.
Understanding operational environments
The platform provides three separate environments, each with a specific purpose:
- Production – The real operational environment, where official data exchanges between parties take place.
- Testing – An environment identical to production, used to test integrations and verify that e-services function correctly before making them available to everyone. Real data must not be used here.
- Validation – A test environment open also to parties that have not yet completed the subscription (e.g., private companies). It uses only simulated data and is intended to familiarize users with the platform’s functionalities.
| Environment name | Authorized for producing | Real data exchanged |
|---|---|---|
| Production | Public Administrations (PA), Public Service Managers (GSP), Publicly Controlled Companies (SCP), Companies within the Consolidated Economic Account (SCEC) | Yes |
| Testing | Public Administrations (PA), Public Service Managers (GSP), Publicly Controlled Companies (SCP), Companies within the Consolidated Economic Account (SCEC) | No |
| Validation | All parties | No |
User and role management
The administrator is responsible for managing the users of their party. They can create or revoke accounts and assign one of three available roles.
User roles
- Administrator – Has full control over the front office. Can manage users, create e-services, manage purposes and service requests, and handle cryptographic material (clients and keys).
- Security Operator – The technical role responsible for managing cryptographic material (e.g., uploading public keys). Cannot manage users or e-services.
- API Operator – The technical role that manages e-services and the technical aspects of purposes. Cannot manage users or cryptographic material.
Permissions
| Activity | Administrator | API Operator | Security Operator |
|---|---|---|---|
| Appoint and revoke Administrators | ✅ | ❌ | ❌ |
| Create and remove operators | ✅ | ❌ | ❌ |
| Manage e-service status | ✅ | ❌ | ❌ |
| Edit e-service attributes | ✅ | ❌ | ❌ |
| Manage e-service creation | ✅ | ✅ | ❌ |
| Submit a service request | ✅ | ❌ | ❌ |
| Manage e-service consumption | ✅ | ✅ | ❌ |
| Manage cryptographic material | ✅ | ✅ | ✅ |
Creating and managing users
The administrator can create new operator or administrator accounts directly from the front office. Detailed procedures for creating and revoking accounts are available in the Tutorial section.
Initial configuration checklist
Upon first access, the administrator is advised to set up the party’s contact information — verifying and entering the contact email address to receive important communications from the platform and from consumers.
Next page → Reference legislation
Hai bisogno di aiuto?
Apri un ticket utilizzando l’apposita funzione all’interno della tua Area Riservata
