Roles and permissions in user management (step 1)
Roles and permissions in user management (step 2)
Roles and permissions on the platform

The three user roles explained: basic user, advanced user and environment administrator. Plus organisation-level permissions.

In brief The platform has three roles (basic user, advanced user, environment administrator) that determine what someone can do at environment level. These are platform roles, separate from the role a member can have within a specific organisation. There are also permissions per organisation and a separate relationship manager role for external collaboration.

The three user roles

Each user in an environment has exactly one platform role. Note: platform roles are separate from the role a user can have within a specific organisation. See Permissions at organisation level for the difference.

Each user has exactly one of these platform roles:

Basic user

The default role for users who are added after the environment already exists. The first user of an environment is always an Environment Administrator. Every subsequent user added via an invitation automatically receives the Basic user role; the Environment Administrator can change this afterwards.

A basic user can view documents, create invoices and send them for the organisations they are a member of. This is sufficient for most employees who work with invoices on a daily basis.

A basic user cannot: invite other users, create or delete organisations, assign roles, or establish partner relationships with other companies.

Advanced user

The advanced user has all the permissions of a basic user, plus the ability to establish partner relationships with other environments. Advanced users are automatically added to a user group, which simplifies user management at organisation level. This is relevant for organisations that collaborate with clients, suppliers or accountants via the platform.

Environment Administrator

The Environment Administrator has full control over the environment. In addition to all permissions of the advanced user, an Environment Administrator can:

  • Invite new users and remove existing users
  • Create and manage organisations
  • Assign roles to other users
  • Grant the relationship manager role
  • Change subscription and settings

When a new environment is created, the first user automatically becomes Environment Administrator. Each subsequent user added via an invitation receives the Basic user role by default; the Environment Administrator can change this afterwards.

You cannot make yourself Environment Administrator. Only another Environment Administrator can assign roles. If you are already an Environment Administrator, no action is needed.

Permissions at organisation level

In addition to the environment role, each user also has permissions at the level of individual organisations. There are two levels:

LevelPermissionsMemberView, create and send documents for this organisationAdministratorAll member permissions, plus: add and remove members from the organisation

A user with the Basic user role at environment level can still be Administrator of a specific organisation; the two levels work independently.

The relationship manager role

The relationship manager role is a supplementary role that is assigned separately by an Environment Administrator. A relationship manager can collaborate with other companies and environments via the partnership model.

This role is needed when you want to:

  • Share documents with external parties
  • Collaborate with accountants or intermediaries
  • Access organisations in a linked partner environment

The relationship manager role is assigned via user management by the Environment Administrator.

Other roles

In addition to the three standard roles and the relationship manager role, there are two specialist roles in the system:

  • Developer: this role is assigned to users who work with the API or build technical integrations. The exact permissions depend on the configuration.
  • Anonymous proxy: a system role used for automated processes and API communication. This role is not manually assigned to end users.

Both roles are visible in user management but are in practice only used in specific integration scenarios.

Changing a role

Only an Environment Administrator can change roles. You cannot change your own role; you need another Environment Administrator for that. Go to My environment > Users, select the user and adjust the role. The change takes effect immediately; the user does not need to log in again.

Ownership for system actions

When the platform performs a system action — such as creating a draft invoice via Email Receiver, a workflow status change or an invoice update — this is always done in the name of the most recently appointed administrator of the organisation.

If that administrator role is revoked, ownership automatically reverts to the previous administrator. This explains why automatically created documents are sometimes linked to a different user than expected. To correct the ownership of such documents: ensure that the desired owner is the most recently appointed administrator of the organisation. This applies to all system actions (Email Receiver, workflow, automatic forwarding), not just Email Receiver.

Practical scenarios

Small company with one employee: you are the Environment Administrator yourself and do not need to configure anything further. You automatically have access to everything.

Company with multiple employees: as the first user, you are the Environment Administrator. Invite colleagues as Basic users and grant them the permissions they need per organisation.

Accountant with multiple clients: set yourself up as Environment Administrator with the relationship manager role. This lets you establish partner relationships with client environments and manage their invoices.

Holding with multiple subsidiaries: all organisations in one environment. Per subsidiary you assign the right employees as member or organisation administrator.


Frequently asked questions
What is the difference between an Environment Administrator and an organisation administrator?

An Environment Administrator manages the entire workspace: inviting users, creating organisations, changing subscriptions. An organisation administrator can only add or remove members from that specific organisation. The two levels work independently: you can be an organisation administrator without being an Environment Administrator.

Can a user be a member of multiple organisations?

Yes, a user can be a member of one or more organisations within the same environment. Only the organisations a user is a member of are visible in the platform. An Environment Administrator or organisation administrator can add members.

Can I set permissions per invoice or per debtor?

No, permissions are set at organisation level. Every member of an organisation can view all incoming and outgoing invoices of that organisation. No distinction between accounts payable and accounts receivable administration is possible on the platform.

A user sees the message 'user not active' — what now?

If an end user sees the message 'user not active' when logging in, the account has been deactivated. Reactivation is self-service by an administrator — no written consent or support intervention is required. eConnect support does not perform user maintenance in customer accounts.

Steps for the administrator:

  1. Open the user overview.
  2. Filter on inactive users.
  3. Click on the three dots on the right next to the user.
  4. Click Activate.

If no one in the organisation has administrator rights, that is the issue to resolve first.

When does a role change become visible to the user?

The role change takes effect immediately. The user does not need to log in again. The browser window may need to be refreshed for the new role to appear in the interface.


Want to invite a colleague or adjust roles? You can manage this in My environment on platform.econnect.eu. You need the Environment Administrator role for this.

Manage your users