Cruxi
Service decision and evidence guide
The acquired help states that each service can link to only one AP, while economic operators can have up to two APs in the stated active/submitted/validation statuses. Those are different limits. Map service ownership before changing or adding an AP.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Sourced criteria · EU · EUDAMED
| Decision or task | What the source describes | What to prepare |
|---|---|---|
| request-the-use-of-a-new-ap / HTML p [7] | Economic Operators can have up to two AP s in active/submitted/connectivity under validation statuses while Competent Authorities, Designating Authorities and Notified Bodies can have only one AP in active/submitted/connectivity under validation statuses. See Annex 3 ( AP statuses) page for further information about the AP statuses. [1] | Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility. |
| request-the-use-of-a-new-ap / HTML p [59] | You will be able to edit the selected services after the activation of your AP . Each service can be linked to only one AP . See section Generate your security key for more information. [2] | Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility. |
Dated technical/help evidence, not a complete legal duty set or live EUDAMED response. Current target-environment release, business rules, permissions and actual buyer records remain unresolved. Blank dictionary flags are unknown; occurrence and update notes keep their stated conditions. No credentials, registration deadline or completed production exchange is inferred.
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Record each actual AP, environment, status and owner rather than counting only active endpoints.
Useful evidence: A current AP/status inventory.
For each required service, record its assigned AP and planned destination; identify assignment conflicts.
Useful evidence: A per-service current/proposed routing table.
Agree activation, token handling, transaction checks and rollback responsibilities before changing assignments.
Useful evidence: A cutover checklist with service-level acceptance evidence.
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
Thu, 27 Aug 2026 11:33:34 GMT · retrieved 2026-10-07
Source key D07 · snapshot 0f08cdf1f24b85ffb86cce43e80560972c8ea4b5ed44456c7185356f88fe0620
Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.