Passer au contenu
Qualified safety assessorsUK · EU · USA
Get a quote
  1. Home
  2. BLOGS
  3. CPNP Login and Access: EU Login, SAAS Roles and Who Should Hold the Keys

CPNP Login and Access: EU Login, SAAS Roles and Who Should Hold the Keys

How CPNP access really works, from EU Login and SAAS to local administrators and sub-organisations, and how to set it up so a resignation or a change of Responsible Person never locks you out.

S Syed Muhammad Shamuel SheesFounder & Lead Compliance Consultant
Updated Nov 19, 2026 13 min read
Reviewed by Phoenix Cosmetic Safety · Oct 31, 2026
Hand holding a phone showing a two-factor verification code next to a laptop login screen, as used for EU Login access to the CPNP

The short answer

CPNP login takes three steps. You create a personal EU Login account, the Commission's sign-in service. You then request CPNP access in SAAS, the Commission's authorisation system, by joining your organisation or creating it with the right profile, usually Responsible Person. Finally you log in to the portal. A brand-new organisation is validated by the Commission, which can take up to two weeks. After that, its local administrator approves everyone else. Only a Responsible Person established in the EU can notify, so a UK or US brand normally works through its EU Responsible Person's organisation rather than its own.

Key takeaways

  • EU Login checks who you are. SAAS decides what you can do in the CPNP. Most "CPNP login" problems are really one or the other, and they are fixed in different places.
  • The Commission asks users not to sign up to EU Login with a generic or shared mailbox. Give each person their own account and build resilience through people, not shared passwords.
  • Whoever creates the organisation in SAAS becomes its local administrator. The Commission encourages every organisation to have at least two.
  • A consultant or contract manufacturer who notifies for a Responsible Person should get a sub-organisation. They can work on notifications, but they cannot see the parent's other products.
  • Changing your organisation's name or country in SAAS after you have notified products makes the CPNP read-only for you until a local administrator justifies the change. Ask CPNP support before touching it.
  • When you change Responsible Person, the outgoing one copies your products across. The copies arrive as drafts with new CPNP references, and the label images and contact person have to be added again.

Most CPNP login problems we are asked to fix are not password problems. They are ownership problems that turn up looking like password problems. The founder who set up the account has left. The Responsible Person has gone quiet. Someone "tidied up" the company name in SAAS and now nothing can be edited. In each case the fix depends on knowing which of three systems you are actually stuck in, and who holds the keys to it.

This guide walks through how CPNP access works in 2026, which role to ask for, how to let a consultant or contract manufacturer in without handing over the whole account, and what to do when it goes wrong. If you would rather have the notification filed for you, our CPNP product notification service can do that work. If you are completely new to the portal, start with what the CPNP is, and if you are wondering whether you need to "register" at all, our piece on CPNP registration versus notification clears that up.

A note on screens

The CPNP screens and menu names change from time to time. For current buttons, use the Commission's CPNP user guide for Responsible Persons and distributors (last updated 18 March 2026) and the tutorials on the CPNP welcome page. This article covers the parts that change far less: identity, organisations, roles and recovery.

How CPNP login works: three systems, not one

The CPNP sits behind two layers. EU Login, formerly called ECAS, is the European Commission's authentication service, used for many Commission applications, not only the CPNP. SAAS is the authorisation system that gives you an organisation, a profile and access rights. Put simply, EU Login says who you are and SAAS says what you may do. Only after both are in place does the portal itself let you in.

StepWhereWhat you doWho approves
1. IdentityEU LoginCreate a personal account with your work email, confirm it within 24 hours, set a password and add a second factorNobody. It is self-service
2. AuthorisationSAASChoose "Cosmetic Products Notification Portal", then join your organisation or create it, and pick one access profileA new organisation: the European Commission. An existing one: its local administrator
3. PortalCPNPClick Log in and sign in with your EU Login detailsNobody. Your SAAS profile decides what you see

Knowing this split saves days. A forgotten password is an EU Login problem. A refused access request, a missing organisation or a read-only warning is a SAAS problem. Sending the wrong team the wrong question is how a one-hour fix becomes a three-week one.

Setting up EU Login for the CPNP

Create the account at EU Login with your own work email. The Commission's EU Login tutorial for CPNP users asks people not to use functional or generic mailboxes, which surprises brands that like to put everything on a shared compliance inbox. The logic is sound: an EU Login is a personal identity, and the CPNP records who did what. Resilience comes from having more than one person with access, not from several people sharing one password.

A few practical points from the tutorial. The activation email has to be confirmed within 24 hours. The password needs at least 10 characters, with at least one capital letter and one number. Two-factor verification is optional for Responsible Person and distributor users, and mandatory for the read-only side used by authorities and poison centres. We recommend switching it on anyway.

If you last set up two-factor a few years ago, check how. The Commission has phased out SMS codes for EU Login, and the CPNP now tells users the SMS option is no longer available. The alternatives are the EU Login mobile app, which the Commission recommends, a national eID, a physical security key or the Trusted Platform Module built into many laptops. A user whose only method was SMS on an old phone will be locked out at exactly the wrong moment. The Commission's EU Login user guide covers changing your email address and verification methods.

Requesting CPNP access in SAAS

Once EU Login works, go to SAAS and request access. The Commission's SAAS tutorial sets out the sequence, and a few choices along the way matter more than they look.

  • Pick the right application. Choose "Cosmetic Products Notification Portal" for a Responsible Person or distributor profile. The "(Read-only)" version is for authorities and poison centres. SAAS manages other Commission systems too, and requests for the wrong one are ignored or rejected.
  • Search before you create. If your organisation already exists, request access to it. The CPNP welcome page warns that duplicated organisations will not be validated. Organisations created in SAAS are also visible to every SAAS user, so spell the name exactly as it appears on your label.
  • Match the label. The Responsible Person details in a notification are pulled from the organisation in SAAS. The Commission's CPNP FAQ says the organisation name must match the Responsible Person details on the product labelling.
  • Choose one profile. Responsible Person, Distributor or Delegate. If you are both a Responsible Person and a distributor, pick Responsible Person, because that profile can also make distribution notifications.
  • Expect a wait for new organisations. According to the new organisation tutorial, the Commission validates you if you are the first local administrator of your company. Everyone after you is approved by that local administrator. The CPNP FAQ says Commission validation can take up to two weeks.

One more rule trips up small teams: all members of an organisation and its sub-organisations must have the same profile. A distributor cannot join a Responsible Person's organisation. It needs its own.

CPNP roles and profiles at a glance

Profile or roleWho it is forWhat it lets you do
Responsible PersonThe EU-established Responsible Person under Article 4, and users acting for itCreate, update and manage notifications under Article 13, and nanomaterial notifications under Article 16
DistributorA distributor that makes a product available in another member state and translates labelling on its own initiativeLink a short Article 13(3) notification to a product the Responsible Person has already notified. It cannot see the Responsible Person's data
Delegate (nanomaterials)A person designated by the Responsible Person for nanomaterial notificationsEnter Article 16 data on request. It cannot notify cosmetic products
Local administratorA role on top of a profile, held by named users of the organisationAccept or reject access requests, edit organisation details, appoint other local administrators, block leavers
Read-only (CPNP Read-only application)Competent authorities and poison centresView notification data for market surveillance or medical treatment. Two-factor sign-in is mandatory for these users

Picking the Responsible Person profile in SAAS does not make anyone a Responsible Person in law. Article 4 of Regulation (EC) No 1223/2009 decides that, and the CPNP welcome page spells out the practical effect: a legal person with its registered office in the EU or EEA, or a natural person resident there. A UK or US company has no route to its own Responsible Person account, whatever it selects. Our guide to whether you need an EU Responsible Person explains the test, and can I be my own Responsible Person? covers setting up your own EU entity.

Who should hold the keys? Three common set-ups

Article 13 puts the duty to notify on the Responsible Person, and notifications live inside the organisation that made them. Every access dispute we have seen comes back to that. So before you worry about passwords, decide whose organisation your products will sit in.

Set-upWhose organisation holds the notificationsTypical forWatch out for
Your own EU company is the Responsible PersonYoursBrands with an EU subsidiary or EU foundersYou carry every Responsible Person duty, and someone has to run the account
A third-party EU Responsible PersonThe provider'sUK, US and other non-EU brandsYour access depends on the provider. Agree the copy and handover terms before you sign
Your Responsible Person plus a sub-organisation for whoever notifiesThe parent Responsible Person's, with drafting done in the sub-organisationEU brands using a consultant, or a Responsible Person working with a contract manufacturerSub-organisations must be approved by the parent's local administrator and cannot see the parent's other products

Take a small UK skincare brand selling into Ireland and Germany through an EU Responsible Person service in Dublin. The brand has no EU company, so the provider's organisation holds the notifications. Most providers that notify for many brands from one organisation will not add client staff as users, for confidentiality reasons. What the brand should ask for instead is a reference list for every product and variant, with CPNP numbers and notification dates, a copy of what was notified, and a contract clause saying the provider will copy the products to a new Responsible Person and hand over the Product Information File within a set number of days if the contract ends. That is the brand's real "access". (This example is a composite of situations we see, not a single client.)

Now a different case. A contract manufacturer in Poland fills products for a German brand, which is its own Responsible Person. The brand wants the manufacturer's regulatory team to prepare the notifications, because they hold the formulas. Adding them as ordinary users of the brand's organisation would show them every product the brand has ever notified, including ranges made by competitors. A sub-organisation solves this.

Giving a consultant or contract manufacturer access the right way

The Commission's CPNP FAQ is direct about it: a sub-organisation has nothing to do with a subsidiary or affiliate. Its purpose is to let an organisation use a contractual company to notify on its behalf. In practice:

  • The sub-organisation is created in SAAS and linked to an organisation that has already been validated.
  • Its users request access with the same profile as the parent, and the parent's local administrator approves both the sub-organisation and its users.
  • In the notification itself, the Responsible Person is always the parent. No sub-organisation data appears, and authorities and poison centres do not see it.
  • Users in a sub-organisation cannot see the parent's notifications or those of other sub-organisations under the same parent.
  • A parent with sub-organisations can move products between them through the Admin menu, but users in a sub-organisation cannot copy products to another Responsible Person.

Keep the legal picture separate from the technical one. A consultant with CPNP access is not your Responsible Person. If your own EU company is the Responsible Person and you approve a consultant to prepare notifications, you still carry the obligations and you can remove them whenever you like. If the consultant is the Responsible Person under a written mandate, their organisation holds everything and your access depends on them. The screens can look identical. Ask any provider which of the two they are offering.

Local administrators: the job nobody knows they have

The first person who creates an organisation in SAAS becomes its local administrator. Often that is a founder in a hurry or a freelancer who has since moved on. Local administrators approve and reject access requests, edit the organisation details and can block or delete users who leave. They can also make another user a local administrator by ticking a box on that user's profile in SAAS.

The Commission's FAQ "warmly encourages" every organisation to have at least two local administrators, and we would treat that as a rule. With only one, a resignation, a long illness or a lost phone freezes your ability to add anyone. Three habits keep this healthy:

  • Remove leavers in SAAS on their last day, as part of the normal offboarding checklist.
  • Review the user list once a year, alongside your annual notification review.
  • Keep your own register outside the CPNP: every product and variant, its CPNP reference, the notification date, the formulation notified and the label version. When access breaks, that register is your evidence of what you are entitled to.

CPNP login problems and where to fix them

What you seeWhich systemWhat usually fixes it
"User not found" at sign-inEU LoginYou registered with another email address. Try it, or create an account if you never had one
Forgotten passwordEU LoginUse "Lost your password?" on the EU Login sign-in page
New phone, no second factorEU LoginRe-register your verification method in your EU Login account. SMS is no longer offered, so use the mobile app, a security key, an eID or your computer's TPM
Login works, but no CPNP accessSAASYour access request is pending or was refused. Ask your local administrator, or for a new organisation, allow up to two weeks for Commission validation
"Details are missing" after loginSAASA local administrator completes the organisation details, especially the full address, in SAAS
CPNP is read-onlySAAS and CPNPThe organisation name or country was changed in SAAS. A local administrator justifies the change in the CPNP
You cannot see products you expectCPNPYou may be in a sub-organisation, or the products sit in another Responsible Person's organisation
Nobody in the business can get inCPNP supportUse the request form on the CPNP site and be ready to show you are the organisation concerned

The last row is the one to avoid. CPNP support can help, but they will want to be sure they are dealing with the organisation concerned, and that takes time. The usual cause is a single local administrator who has left, and a second administrator prevents it.

Renaming or moving your company: the read-only trap

This one catches growing brands. The Commission's user guide warns Responsible Persons never to change the organisation name or country in SAAS once products are notified, because authorities need to find products under the name that was on the label. If the name or country is changed anyway, the CPNP becomes read-only for the whole organisation until a local administrator logs in and justifies the change.

According to the CPNP FAQ, the name can be edited for genuine corrections, such as a typo, or when the organisation has not yet notified anything. A real change of name or country after notifying usually means creating a new organisation and copying the products across. Changing name and country at the same time is not allowed at all, and moving the organisation to a non-EU country ends its Responsible Person access. Before you touch anything, ask CPNP support through the request form which route applies. Address and phone changes are simpler and, the FAQ says, take about 10 minutes to sync from SAAS to the CPNP.

Changing Responsible Person without losing your notifications

The CPNP Admin menu has a function called "Copy your products to another Responsible Person". Only users in a main Responsible Person organisation can run it, which in practice means the outgoing Responsible Person. They search for the new Responsible Person by name or system ID, select the products and confirm. Per the user guide, the copies land in the new organisation as drafts with new CPNP references. Everything is copied except the packaging and labelling information and the contact person details. The originals stay where they were, marked as copied.

  1. Appoint the new Responsible Person first. Products need a valid Responsible Person throughout, so do not let the old arrangement lapse early.
  2. Get the full reference list. Every product, variant, CPNP reference and notification date, in writing.
  3. Agree who runs the copy and by when. This is where a handover clause agreed at the start pays for itself.
  4. Take delivery of the Product Information File. Complete, including claims support and any records of undesirable effects.
  5. Complete and submit the drafts. The new Responsible Person adds the new label images and contact person.
  6. Change the artwork. The Responsible Person name and address on the pack must change, so plan stock run-out with both parties.
  7. Check against your register. Late-added shades and scents are the ones most often missed.

If the outgoing provider will not run the copy, the new Responsible Person notifies the products again from scratch. That is slower and needs the full data, which is one more reason to keep your own register. For ranges, our guide to notifying cosmetic variants explains what counts as a separate notification.

Great Britain runs on a different login

Great Britain uses SCPN, run by OPSS, and it has nothing to do with EU Login or SAAS. SCPN now signs users in through GOV.UK One Login. The One Login email address has to match the SCPN account email. If it does not, you create a new, empty SCPN account, and OPSS asks you to contact them through its enquiries form to fix it. Security codes now come from One Login, not SCPN. A brand selling in both markets therefore has two sets of access, often with two providers, and the same governance questions twice. Our SCPN vs CPNP comparison covers running the two side by side, and the Northern Ireland guide explains why NI follows the CPNP route.

A five-minute CPNP access check

  • We know which CPNP organisation holds each of our notifications.
  • Every user has their own EU Login on a named work email, and nobody relies on SMS codes.
  • Our organisation, or our Responsible Person's, has at least two local administrators.
  • Anyone who notifies for us from outside the organisation works in a sub-organisation.
  • We hold our own register of CPNP references, dates and label versions.
  • Our Responsible Person contract covers copying products and handing over the Product Information File.
  • Nobody edits the organisation name or country in SAAS without checking with CPNP support first.
  • Our SCPN access matches our GOV.UK One Login email.

If you are budgeting a launch, our breakdown of what CPNP notification actually costs shows where the Responsible Person fee fits. And if you would rather not run any of this yourself, our EU Responsible Person and CPNP notification service keeps the access, the register and the handover terms in order for you.

Related reading on the Phoenix blog

Myths we hear

  • A UK or US brand can open its own CPNP account and notify. The CPNP is only open to a Responsible Person established in the EU (or EEA), distributors, authorities and poison centres. A non-EU brand works through an EU Responsible Person.
  • A shared compliance inbox is the safest EU Login. The Commission asks people not to register EU Login with functional or generic mailboxes. Named accounts plus two local administrators is the safer set-up.
  • Giving my consultant CPNP access makes them my Responsible Person. Access is a permission inside SAAS. The Responsible Person role comes from Article 4 and, for a third party, a written mandate.
  • Our notifications belong to our brand, wherever they sit. They sit in the CPNP organisation that created them. Getting them out depends on that organisation running the copy function.
  • Updating the company name in SAAS is just admin. After products are notified, a name or country change locks the organisation to read-only until it is justified, and a genuine change usually means a new organisation.

What to do this week

  1. List who holds CPNP access today, in which organisation, and who the local administrators are.
  2. Make sure every user has their own EU Login on a named work email, with a mobile app, security key or similar second factor. SMS codes are no longer offered.
  3. Appoint a second local administrator, or ask your Responsible Person who theirs are.
  4. Put any consultant or contract manufacturer who notifies for you in a sub-organisation, not in the parent organisation.
  5. Keep your own register of every product, CPNP reference, notification date and label version.
  6. Add a clause to your Responsible Person contract covering the copy of your products and the handover of the Product Information File if the contract ends.
  7. Before any company name, address or country change, check the SAAS rules and ask CPNP support for the correct route.
  8. Run the same checks for SCPN and GOV.UK One Login if you also sell in Great Britain.

Frequently asked questions

How do I log in to the CPNP?

You need an EU Login account and an active CPNP profile in SAAS. Once both are in place, go to the CPNP portal, click Log in, and sign in with your EU Login email address and password, plus your second factor if you have set one up. If the login works but you see no CPNP screens, the problem is your SAAS access, not your password.

Can a UK or US company get its own CPNP access?

Not as a Responsible Person. The Commission's CPNP pages say only a Responsible Person can notify, meaning a legal person with its registered office in the EU or EEA, or a natural person resident there. A UK or US brand appoints an EU Responsible Person or sets up an EU company, and that organisation holds the CPNP access.

How long does CPNP access take to approve?

If you are joining an organisation that already exists, its local administrator approves you, so it can be the same day. A brand-new organisation has to be validated by the European Commission first, and the CPNP FAQ says that can take up to two weeks. Build that into your launch plan.

Who is the local administrator in the CPNP?

The first person to create an organisation in SAAS becomes its local administrator once the organisation is validated. Local administrators accept or reject access requests, edit the organisation details and can block leavers. The Commission recommends at least two per organisation, and an existing local administrator can tick the box to make another user one.

How do I give my consultant or contract manufacturer access to the CPNP?

If they notify on your behalf, the cleanest route is a sub-organisation linked to your Responsible Person organisation. They request access to it, your local administrator approves it, and the notifications still show your organisation as the Responsible Person. Sub-organisation users cannot see the parent's notifications or those of other sub-organisations.

Should our EU Login be on a shared company inbox?

No. The Commission's own tutorial asks users not to register EU Login with functional or generic mailboxes. Give each person their own account on a work email, make at least two of them local administrators, and remove leavers in SAAS on their last day.

Why has the CPNP become read-only for my organisation?

It usually means someone changed the organisation's name or country in SAAS after products had been notified. A local administrator has to log in to the CPNP and justify the change before anyone can edit again. Some changes, such as a merger, mean creating a new organisation instead, so contact CPNP support through the request form before you edit anything.

What happens to my CPNP notifications if I change Responsible Person?

The outgoing Responsible Person uses the CPNP function that copies products to another Responsible Person. Your products arrive in the new organisation as drafts with new CPNP references. The packaging and labelling images and the contact person are not copied, so the new Responsible Person adds them and submits. If no copy is made, the products are notified again.

Official sources and legislation

S
Written by

Syed Muhammad Shamuel Shees

Founder & Lead Compliance Consultant

Phoenix Safety Consultants is a cosmetic compliance consultancy with offices in London, Tallinn and Pensacola. Our safety assessors and toxicologists prepare CPSRs, Toxicological Risk Assessments, PIFs, SDSs and UK/EU notifications for brands of every size. Talk to the team on WhatsApp or at compliance@phoenixcosmeticsafety.com.

Join the conversation