Skip to main content

Inviting Your Team to Walls.io Echo

Add more team members to your Echo account

Written by Michael Kamleitner

Walls.io Echo allows you to make event promotion a team effort. Inviting a colleague takes under a minute, and once they join, you can work on the same campaigns together. Every member sees the same campaigns, folders, and analytics, each with a role that decides what they are allowed to do.

🔎 Please note: Billing is per organisation, not per person. The subscription belongs to the organisation, so every member works under the same plan. Inviting teammates never costs extra.


Inviting a team member

  1. In your Dashboard, go to Organisation Settings → Members (available to admins and owners).

  2. Click Invite member.

In the dialog that opens:

  1. Enter the colleague's email address and pick a role. You will find a detailed explanation of each role below.

  2. Click Submit. Walls.io Echo emails the invitee a secure, single-use invitation link that stays valid for one week.

A few details worth knowing:

  • The invitation is tied to the exact email address it was sent to. It can only be accepted by an account using that address, so a forwarded link will not work.

  • An address that already belongs to a member can't be invited — change their role from the members list instead.

  • Granting the Owner role asks for an explicit confirmation, because a new owner gets full control of the organization.​

  • If an invited member is new to Echo, the link takes them straight to a short sign-up form to enter their name and password.

Roles: Editor, Admin, and Owner

Every member has one of three roles.

Role

What they can do

Editor

Full day-to-day work: create, edit, reorder, and delete campaigns, their sharing visuals, and folders. Editors have complete campaign and folder access, but they can't manage members or change organization settings.

Admin

Everything an editor can do, plus manage the team: invite new members, change members' roles, and remove members.

Owner

Everything an admin can do, plus change organisation settings: rename the organisation, manage its custom fonts, delete it, manage its subscription and billing, and grant the owner role to share ownership with another member.

Keeping track of team members

1. The role the user was assigned.

2. Status: Until an invitation is accepted, it appears in the Members list with a Pending badge. Users who have accepted the link are Active.

3. Change role or Remove:

  • Change: Pick the new role from the members list. An organisation must always keep at least one owner.

  • Remove: Removing someone from the Members list immediately revokes the API tokens and connected apps they used.

4. For Members who are still pending:

  • Resend: Sends the same invitation email again; the original link keeps working.

  • Delete: Withdraws the invitation immediately. Its link stops working the moment you delete it.


Switching Between Organisations

If you belong to more than one organisation, an organisation switcher appears at the top of the Dashboard sidebar. Use it to choose which organisation you're working in — the campaigns, folders, and analytics you see always belong to the organisation you have selected.



Organisations in the API and MCP Server

Your organisation reaches beyond the Dashboard. Both the REST API and the MCP server act within a single organisation, so automations and AI assistants see exactly the campaigns and folders that organisation owns. The two surfaces give you comparable access to your organisation's campaigns and folders — the same bound-organisation semantics — but they differ in two ways.

First, in what carries the binding: a REST API token is tied to one organisation when you create it, while an MCP connection is tied to one organisation per connected app.

Second, in organisation discovery: the REST API can list all the organisations you belong to (through its GET /v1/organisations endpoint), while the MCP server shows only the organisation its connection is bound to, plus whether you belong to others. Managing members stays in the Dashboard — it isn't available on the API or through the MCP server.

💡 Tip: To automate against a specific organisation, create an API token for it under Settings → API, or connect an AI assistant and pick its organisation under Settings → Connected apps. See the REST API and MCP server guides for details.

If you have further questions, don't hesitate to contact the support team via chat or support@walls.io!

Did this answer your question?