Table of contents
Delegations
What they are and how they work
Delegations allow a party to entrust another party with the administrative management of the producing or consuming of an e-service. Delegations concern only administrative functions: any technical or operational agreements with technology partners for producing or consuming APIs remain outside the scope of the delegation.
Availability by environment
- Testing and Production: the feature is available to parties qualified as Public Administrations in the IPA Catalog.
- Validation: the feature is available to all parties.
Ownership and responsibilities
With a delegation, the ownership of objects and administrative responsibility toward third parties remain with the delegating party.
Delegation stages
- Make availability known — Party A makes its capacity to receive delegations available, specifying the scope: producing or consuming.
- Send the delegation — Party B creates and sends to A a delegation request for producing or consuming a specific e-service.
- Accept or reject — Party A accepts the delegation (or rejects it, providing a reason).
- Operational management — Party A manages the administrative activities related to producing or consuming on behalf of party B. For the delegated object, party B no longer manages administrative activities.
- Revoke — At any time, party B may revoke the delegation and regain control of the delegated objects.
Next page → Operations and lifecycle
