Skip to content

Invite team members

People are invited into a seller profile, not into Vendlen generally. Access is per seller, and someone working across two sellers is invited to each. Only the seller owner manages the team.

The Users tab lists everyone with access and the role each of them holds, along with the seats used against your plan’s limit. Invite member sends a one-time link by email. At the seat limit, remove a member or a pending invitation, or upgrade the plan, before inviting someone else.

Invitations still waiting are listed with their expiry date, and Cancel invitation makes a link invalid straight away.

The member list shows each person’s role. That is the fastest way to answer “who can send changes to Amazon?” without opening every profile in turn.

An invitation grants no view or edit access. The person joins with no permissions, and you grant them once they have accepted: select the member and set each area.

The safe default is View, one click under Quick set. Someone who can read the account can learn it, form opinions and tell you what they would do, without being able to spend anything. Raise what they need when they need it.

The permission that matters most is Automation — see Roles and permissions for what each area allows and which ones reach your live Amazon account.

Remove from seller revokes access immediately and cancels any invitation still waiting for that person on this seller. Their Vendlen account is kept and still works with other sellers.

Two things it does not do:

  • It does not undo what they did. Changes they sent to Amazon are in Change History, and remain in the account until something changes them back.
  • It does not turn off what they set running. A rule they enabled keeps running after they are gone. When someone with Automation Edit leaves, review the rules before you close the tab.
  • Each person should have their own account. Shared logins make Change History useless — every change looks like it came from the same person, which defeats the point of recording a source.
  • Everyone with access should have their own two-step verification enabled.
  • On a long member list, search matches name, email, or role, so you can find everyone holding a particular role rather than checking one by one.