Skip to main content

Workspace setup

This guide walks through the first objects you create in the portal before you send or receive traffic through the API. Read Test vs. Live mode first so you work in Test until you are ready for production.

1. Team​

A team is your workspace: it owns companies, participants, and documents. Users are invited to a team with a role (Owner, Admin, Developer, or Read-only).

Create a team

  • Sign in to the portal.
  • If you do not have a team yet, use Create team (team registration) and enter a team name. You become the Owner of that team.
  • If someone invited you by email, open the invitation link and accept; you join their team instead.

You can belong to more than one team and switch between them from the team menu.

2. Team members and invites​

Owner and Admin can manage who belongs to the team. Developer and Read-only cannot open team settings.

  1. With the team selected in the portal, open Team settings from the team menu.

  2. In the settings sidebar, open Members.

  3. Use Invite member to send an email invitation. Choose a role:

    • Admin — companies, participants, team settings, API keys, webhooks
    • Developer — API keys, webhooks, companies, and participants (not team membership or team name/slug)
    • Read-only — view access; cannot change integration settings

    The Owner role is not available on invitations (the person who creates the team becomes Owner).

Pending invitations appear in the table until the recipient accepts. You can change a member’s role or remove them from the team. The last Owner cannot be removed or demoted—another Owner must exist first.

Details, also in the settings sidebar, lets Owner and Admin edit the team name and slug.

3. Company​

A company is a legal entity inside the team. Participants (network addresses) are attached to a company.

Create a company

  1. In the sidebar, open Network → Companies.
  2. Create a new company and fill in at least:
    • Company name
    • Country
    • Company number (your official business identifier for that country, e.g. CVR in Denmark)
    • Signer first name, Signer last name, and Signer title for the person authorised to act for the company
  3. Open the company and use Sign agreement to open the authorisation flow. The agreement must be marked signed before New participant becomes available.

ERP's and other systems that use eCourier on behalf of their users, can also onboard customers through the API. See Customer authorisation and participant registration for both flows and the distinction between signing.

Owner, Admin, and Developer can create or edit companies.

4. Participants​

A participant is your address on Peppol and/or NemHandel so others can route documents to you (and so you can send as that identity). Participants belong to a company.

Add a participant

  1. Open Network → Companies and select the company.
  2. Open the Participants tab.
  3. Once the company's authorisation is signed, use New participant, choose channel(s) (Peppol, NemHandel, or both, where supported), and choose a Participant scheme and Participant ID. The same identifier is used across the selected channels.

Registration with the network is handled asynchronously; creating the participant does not mean it is already active. Check the participant's channel status and any errors in the portal. Use Test mode in the header mode toggle while you integrate; use Live only when you are ready for production traffic.

Owner, Admin, and Developer can add or change participants for a company.

Next steps​

  • API keys for your systems.
  • Webhooks — optional real-time notifications (Developers → Webhooks in the portal).
  • Sending and Receiving — how documents flow through the API.
  • Status: incident history and uptime are published at status.ecourier.io.