UUM&DS Roles.
Access with purpose.
Being identified is not the same as being authorised to act.
UUM&DS supports the management of user access to EU customs information systems. Roles and permissions help determine which services and functions a recognised user may access, within the applicable national and EU-level arrangements.
Core principle Authentication establishes identity. Authorisation determines permitted actions.
Four concepts.
One access decision.
A user’s access to a customs application is not determined by their identity alone. The relevant system must also recognise the applicable permissions and the context in which the user intends to act.
User
The individual whose identity is recognised during authentication. A user may need access in a particular business or organisational capacity.
Role
A defined access profile used within an applicable authorisation arrangement. Its meaning and available functions depend on the relevant customs service.
Permission
The ability to perform a particular operation or access a function, where that capability is supported and authorised by the application.
Organisation context
The economic operator or other entity in whose relevant capacity a user acts, where the service requires an organisational relationship.
Same user. Different permitted actions.
The following example demonstrates how access scope can differ. It does not reproduce official UUM&DS role names or permissions.
| Illustrative activity | Profile A | Profile B | Profile C |
|---|---|---|---|
| View application records | Permitted | Permitted | Permitted |
| Prepare application data | Not permitted | Permitted | Permitted |
| Submit an application | Not permitted | Not permitted | Permitted |
Profiles A, B and C are fictional examples. Actual roles, functions and permission combinations must be checked against the relevant customs application and competent authority’s instructions.
Permission is never just a label.
A role or permission must be interpreted within the service for which it applies. Access to one customs application does not automatically imply access to another, even when both use the UUM&DS framework.
The specific EU customs service concerned.
The relevant trader or entity, where applicable.
The function the user is authorised to perform.
Who grants access?
Understanding the responsibility chain.
Customs application permissions are managed within defined administrative and technical arrangements. The economic operator, authorised organisational users and competent national authorities may have different responsibilities depending on the service and Member State.
The organisation
Identifies its operational access needs, determines which individuals should act on its behalf and follows the applicable procedures for requesting or managing access.
The designated administrator
Where supported by the relevant access arrangement, an authorised administrator may manage user permissions or submit access requests within the limits of their own authority.
National customs administration
The competent national authority establishes or operates the applicable access arrangements and may be involved in registration, approval, administration or support, depending on the system.
These are responsibility categories, not a mandatory three-step approval sequence. Some services or national implementations use different administrative arrangements.
Access should follow operational need.
An effective permission-management process does not end when access is first granted. Permissions should remain appropriate throughout the user’s relationship with the organisation.
Identify the requirement
Determine the customs application, business purpose and activities for which access is required.
Follow the applicable access procedure
Submit or manage the request through the authorised national or application process, where required.
Confirm the permitted scope
Verify that the user can perform the necessary functions without receiving unnecessary privileges.
Review and adjust access
Reassess permissions when duties, organisational relationships or application requirements change.
Remove obsolete permissions
Arrange for access to be withdrawn when the underlying business need or authorisation no longer exists.
Requesting access is not the same as granting it.
An employee may need a particular customs function, and an organisation may support that request. Neither fact alone establishes that the individual has the necessary system permissions.
The authorisation becomes effective only through the relevant access-management arrangements and remains subject to the applicable service conditions.
Consult the European Commission’s UUM&DS information and the competent national authority for service-specific access procedures.
Different operators.
Different access requirements.
Customs activities involve employees, representatives and organisations operating across different digital services. Their business responsibilities do not automatically establish the permissions available in a particular customs application.
Employee of an importer
An employee needs to perform customs-related tasks for the company that employs them.
INTERNAL USERIndividual identity
The employee authenticates using the identity route supported by the relevant customs service.
Organisational relationship
The applicable access arrangement must recognise the employee’s authority to act in the company’s relevant capacity.
Application permissions
The employee needs the permissions required for the intended functions, which may differ between applications.
Employment by an EORI-registered company does not automatically grant access to all customs systems or functions.
Customs representative
A customs service provider acts for a client under an appropriate representation arrangement.
EXTERNAL OPERATORCustoms representation
The representative’s authority to act for a client must be established under the applicable customs representation rules.
Digital access arrangements
Where the application requires an electronic delegation or another access relationship, that requirement must also be satisfied.
Permitted application functions
The representative must have access to the functions needed for the relevant service, subject to its rules.
Customs representation and electronic access authorisation are related but distinct matters. One does not automatically replace the other.
Multi-system customs user
One person needs to work with several EU customs applications for different operational purposes.
MULTIPLE SERVICESShared identity infrastructure
Different services may rely on a common authentication or user-management framework.
Separate access requirements
Each application can define its own eligibility conditions, access profiles and permitted operations.
Independent access outcomes
Being able to use one service does not prove that the user is authorised to use another.
A recognised identity can support access across services, but the relevant permissions must still be established for each application.
Two different questions must be answered.
This depends on the applicable legal relationship, representation arrangements and customs requirements.
This depends on the authentication and authorisation requirements of the relevant digital service.
A valid technical permission does not, by itself, establish a legal mandate to represent a trader. Equally, a legal mandate does not automatically provide access to every customs IT system.
Working on behalf of another organisation?
Electronic delegation introduces additional access relationships. Explore the dedicated UUM&DS delegation guide for that topic.
Give users what they need.
Not everything they could access.
The principle of least privilege helps organisations limit unnecessary access to customs applications. Permissions should reflect actual responsibilities, be reviewed when circumstances change and remain proportionate to the operations users need to perform.
Access based on operational necessity.
An employee who only needs to consult application records should not automatically receive permissions to submit, modify or administer those records.
The exact separation of functions depends on the application. Where a service does not offer granular permissions, the organisation should assess the resulting access risk and apply suitable controls.
The target is the minimum appropriate access scope, not the maximum available permission set.
Maintain an access register.
A simple internal record helps an organisation understand who is expected to access which customs services. It is a governance tool, not a substitute for official system records.
| Record field | What to document | Why it matters |
|---|---|---|
| User | Individual assigned to the activity | Establishes internal accountability |
| Customs service | Relevant application or system | Separates access across services |
| Business capacity | Organisation or entity concerned | Clarifies the context of use |
| Permission scope | Actual functions or assigned profile | Helps identify excessive access |
| Internal owner | Person responsible for reviewing the need | Supports timely decisions |
| Review information | Last check and any required follow-up | Helps prevent outdated permissions |
This is a recommended internal control model, not a prescribed UUM&DS register or an EU-wide legal reporting requirement. Avoid recording passwords, authentication secrets or unnecessary personal data.
When should access be reassessed?
A fixed review schedule can be useful, but certain operational events should prompt an additional check.
Change of responsibilities
A user moves to a different function or no longer needs certain operations.
New customs application
The organisation introduces a service with its own access requirements.
Change of client or business relationship
A relevant organisational relationship begins, changes or ends.
Departure or extended inactivity
An individual leaves the organisation or no longer has an operational reason to retain access.
Three questions for every permission.
Confirm that the underlying business activity still exists.
Compare the granted functions with the user’s actual duties.
Identify who can approve the continued business need and arrange any changes.
Access governance is an organisational practice. The ability to modify permissions remains subject to the relevant application and national arrangements.
Roles & permissions.
Questions worth answering.
Understand the practical limits of customs access permissions, consult official guidance and continue exploring the related UUM&DS topics.
What should users know?
These answers describe general access principles. Actual role names, procedures and available functions depend on the customs service and national arrangements.
Does every EU customs application use the same roles?
No. Customs applications can have different access profiles, functions and authorisation requirements. A role relevant to one service should not be assumed to exist or have the same meaning in another.
Can an EORI number automatically grant user permissions?
No. An EORI number identifies an economic operator. It does not, by itself, establish an individual user’s permissions in a customs application.
Can one individual have access to several customs services?
Yes, where the applicable access requirements are satisfied. However, permissions for each service must be considered separately and are not necessarily transferable between applications.
Who can change a user’s customs permissions?
This depends on the relevant service and Member State arrangements. Changes may involve an authorised organisational administrator, the competent national authority or another designated access-management process.
Is a UUM&DS role the same as a delegation?
Not necessarily. A role concerns the permissions associated with a user or access context. Delegation concerns an arrangement through which authority or access may be conferred on another party, where supported by the service.
What if authentication succeeds but access is denied?
Successful authentication does not guarantee application authorisation. Check the service-specific access requirements and contact the designated support channel or competent authority where necessary.
European Commission guidance
Consult official sources when verifying access requirements or looking for service-specific instructions.
Official information about the EU customs user-management and digital signatures framework.
View official guidance CUSTOMS SERVICES European Commission Online ServicesFind EU customs services and the associated information provided by the European Commission.
Explore online servicesA recognised user needs the right permissions for the right customs service.
Effective access depends on the applicable identity, organisational and authorisation arrangements. Always verify the specific service requirements rather than assuming that one role provides universal customs access.
This page provides general educational information. Actual access roles, approval procedures and available permissions depend on the relevant customs system and national arrangements. Consult official service documentation and the competent authority for current requirements.