By default your eConnect account is linked to the username you registered with. A username always takes the form of an email address, but in this context it is not used to send or receive email -- only to log in and use other system functionality.

Want to submit invoices from a different address, or log in with a second username? You can add an extra username to your profile. This is only possible for addresses within the same domain as your existing username.

There are several situations where an extra username is useful:

• You want to submit invoices by email from an address other than your main username (for example a shared administration address).
• You want to log in to the platform with an alternative username.
• Your organisation uses multiple addresses within the same domain.

Note: you can only add a username that falls under the same domain as your existing username. Want to link an address with a different domain? Read Email address with a different domain further down this page.

Note: the verification link has a limited validity. Already clicked the verification email but the yellow exclamation mark stays? Refresh the screen first -- sometimes the profile does not update the status immediately. If the mark remains after refreshing, the link has likely expired or was not fully completed. In that case, contact support@econnect.eu to have a new verification email sent.

After adding an extra email address you can:

• Log in to the platform with both your original and your new email address. The permissions and environment remain identical.
• Submit invoices by email from the new address, provided the Email Receiver accepts this address as a trusted sender.

The extra email address is treated as a full alternative to your main address. There is no difference in permissions or functionality.

You can only add a username that falls under the same domain as your existing username. If you want to link an email address with a different domain, that domain must be configured as a shared domain in your environment.

When multi-domain / shared domain is relevant:

• Companies with domain variants (for example .com and .nl)
• Merged organisations that want to keep both domains
• Different brand names under one environment
• Software partners who want users with different domain names to access the same eConnect environment

Example: without shared domains only @abc.com (domain owner) can be added; @abc.nl cannot. With shared domains both can, provided users are invited explicitly.

As a user you cannot configure this yourself. Only the Administrator of your environment can contact Support or Delivery to have this configured. Explicit customer consent is required before domains are made shared: the access structure changes and new users must then be invited explicitly (automatic linking based on domain no longer applies).

Special case: if the other domain already has its own, non-shared environment with a different Administrator, both Administrators must give explicit consent before Support can set both domains as shared. Contact support@econnect.eu for more information.

Setting a shared domain is irreversible and has several important consequences:

• Self-registration after shared domain is set: if a user still tries to self-register after a shared domain is configured (with or without invitation), a separate 'loose' environment is created without access to the organisation. Removing such an incorrectly created loose environment can take several days before correct, manual addition by the Administrator is possible.
• No partner constructions: with a shared domain it is not possible to set up partner constructions between different environments. This is especially relevant for accountants and software partners who serve multiple customers -- they then need a separate login for each customer, not one overarching access.

If a user has accidentally self-registered on a domain that belongs exclusively to one customer environment, the cleanup follows the same shared-domain configuration:

1. Support or Delivery makes the domain shared. Customer consent from the environment owner remains mandatory; communicate in advance that this is irreversible and brings the partner-construction limitation.
2. The unintended user (without organisation access) is removed from the existing environment. As long as there is no link to an organisation, that user sees nothing anyway.
3. A new, separate environment is created for the affected user on the same domain. After shared domain is set, automatic linking no longer applies; new users are explicitly invited from then on.
4. Communication with the affected user about this process goes via Support, not via the customer or partner who reported it.

Impact on the existing environment: with a clean cleanup (only removing the unintended user + creating a separate environment for that user), nothing structurally changes to the access or setup of the existing environment, provided no other changes are made. All other shared-domain consequences described above (no partner constructions, irreversibility) continue to apply.

This article is about adding an extra email address to your user account. That is different from setting up a trusted sender in the Email Receiver. The Email Receiver determines which external email addresses may submit invoices to your organisation. The extra email address on your account determines which addresses you can use to log in and submit.

The domain restriction (same domain only) applies only to email receivers of type ALL_IN_VERIFIED -- these are receivers that only accept email from verified users within the environment. For receivers of type ACCEPT_ALL or SPECIFIC_ADDRESS this restriction does not apply.

Looking for information about setting up trusted senders? Read Email Receiver: the dashboard and sender management.

Want to change your primary email address instead of adding an extra one? Read Change your account email address.