Give every person their own login, and only the access they need

Your warehouse team, your accountant and your customer-service agents should not share one password. easySales lets you invite each of them as a team member with their own credentials, their own permissions, and their own trail of what they did.

  • Individual credentials for every team member
  • Roles plus granular per-section permissions
  • Every action attributed to the person who took it
No card required
Team screen listing members with their roles and whether they are active or still invited My team Active Invited MEMBER ROLE STATE Ana P. Warehouse Active Mihai D. Support Active Elena R. Accounting Active Radu T. Warehouse Invited

HOW IT WORKS

Three steps to a properly staffed account

Start from a role, then tighten it where you need to.

1

Send an invitation

Invite a colleague by email. They set their own password and log in as themselves, so nobody is passing the owner account around the warehouse.

2

Assign a role

Roles bundle the permissions a job normally needs — warehouse, support, accounting — so a new starter is productive without you configuring dozens of switches.

3

Tighten the details

On top of the role, grant or revoke access section by section, and limit which order statuses that person is allowed to work with.

TEAM ACCESS

Access that matches the job, not the account

Permissions are the difference between delegating work and handing over the keys.

01

Roles for the common cases

Most teams have the same handful of jobs, so easySales ships roles that already carry a sensible permission set. Assign one and the person can do their work without seeing your financials, your API keys or your subscription.

Prebuilt roles Sensible defaults Fast onboarding
Diagram showing an invited team member being assigned a role that grants a permission set Trigger Invitation accepted Condition Role assigned Action Permissions applied
02

Per-section permissions when a role is not enough

Real teams have exceptions. Grant a warehouse lead access to supplier orders, keep pricing away from a temporary agent, or open reports to your accountant without opening anything else. Permissions are granular per section, on top of whatever the role sets.

Granular switches Per-section Additive to roles
Permission editor showing full, view-only and no access across different sections for a warehouse role Permissions Warehouse role SECTION ACCESS Orders Full Pick & pack Full Supplier orders View Pricing None
03

Limit which orders a person can touch

Order-status limits let you scope someone to the part of the pipeline they own. A packing operator works the orders that are ready to pack; they do not get to reopen a completed order or cancel one that is already invoiced.

Order-status limits Scoped workload Fewer mistakes
Diagram showing an order action checked against a team member status limit before being allowed Trigger Team member opens an order Condition Status within their limit Action Allow the action
04

Know who did what

Actions are attributed to the individual, not just to the account. Who picked that order, who scanned that parcel, who generated that invoice — the order history names the person, which is what makes delegation reviewable rather than a leap of faith.

Per-employee history Warehouse attribution Audit trail

See pick & pack →

Order action history naming which team member performed each step and when Order history #300429 ACTION BY WHEN Picked Ana P. 09:14 Packed Ana P. 09:31 AWB generated Mihai D. 09:33 Invoice issued Elena R. 09:35

One team, working every marketplace and online store you sell on

5 stars

"No more shared password"

5 stars

"We know who did it"

5 stars

"Onboarding takes minutes"

No card required
14-day free trial
Cancel anytime

Ready to stop sharing one login?

Invite your team, give each person the right access, and see exactly who did what.

Start free trial

Frequently Asked Questions

Have a question? Contact us and we'll be happy to help.

The number of team members is set by your plan, so higher tiers allow larger teams. If you need more seats than your current plan allows, upgrading raises the limit immediately.

Yes. Each person is invited by email and sets their own credentials, which is what makes per-person attribution meaningful in the first place.

Yes. The role sets the baseline and per-section permissions adjust it, so you can start from "warehouse" and then grant or revoke individual areas without building a whole new role.

Yes. Order-status limits restrict a team member to the statuses relevant to their job, so a packer cannot reopen or cancel orders that have already moved past them.

Yes. Actions such as picking, packing, scanning and document generation are recorded against the individual team member in the order history, not just against the account.

Only if you grant it. Some settings are deliberately owner-only, so a team member changing them has no effect — if a setting is not taking hold, check whether it needs to be saved from the owner account.