Marketplace Integration Security: 2FA and Roles

Security in marketplace integration rests on three foundations: a personal account with two-factor authentication for every user, roles limited to each person's job, and controlled management of marketplace API keys. Because the integration panel can write stock and prices to all of your channels from one place, it is a more valuable target than any single marketplace account. This article gives rules you can apply without technical knowledge, plus a checklist.

Why the integration panel is a critical target

If one marketplace account is compromised, the damage stays on that channel. If the integration panel is compromised, one action can zero out prices on every channel, alter stock, or export customer data. And an attacker does not need to break in from outside; the most common scenario is a shared password everyone knows and an employee who has left the company.

That is why the first security question when choosing an integrator should be "are there roles and 2FA?"; it is question thirteen in 15 questions to ask before choosing an integrator. In Bulutegra, user roles and two-factor authentication are standard parts of the Integration Panel.

Rule 1: one account per person, 2FA for everyone

A shared account is the most common and most dangerous habit. If there is a user called "office" with a password everyone knows, nobody can tell who did what, and when one person leaves, the password has to change for everyone.

Steps to apply:

1. Create a separate user for each employee in the panel, with their own name and email.
2. Make two-factor authentication mandatory for every user. An authenticator app is safer than SMS.
3. Store backup codes somewhere safe; if a phone is lost they are the only way in.
4. Do not use the admin account for daily work. Give the admin a second, narrower account for routine tasks.
5. Use a password manager; never share passwords by email or chat.

One-line rule: for every action in the panel, the answer to "who did this?" must be exactly one person.

Rule 2: permissions follow the job

Role-based access means each user sees only the screens their job needs and can write only in those areas. Bulutegra ships with six roles; the first four cover most sellers:

• Admin: every screen, user management, channel connections, ownership flags, write-access handover.
• Content: product data, titles, descriptions, images, the quality tab. Cannot write prices or stock.
• Warehouse: orders, shipping, return intake, barcode-based warehouse actions. Cannot change prices or touch channel connections.
• Accounting: payouts and reconciliation, profitability, reports, CSV export. Cannot write to products or stock.
• Returns: return intake and the returns process; sees orders and can transfer them to the ERP.
• Reporting: the dashboard summary and reports only. Cannot change anything.

When assigning a role, ask:

• Which screens does this person need to look at to do their job?
• Which fields do they need to write? Viewing and writing are different.
• What is the worst mistake they could make by accident with this permission?

Price writing and channel connection changes are the permissions to keep narrowest. If you grant temporary access for a sales event, revoke it when the event ends; this comes up again in managing stock and prices during sales events.

Rule 3: API keys and channel authorizations

The integration connects to marketplaces on your behalf with API keys. Those keys are as valuable as passwords.

• Enter keys only into the integration panel; never in email, chat, or spreadsheets.
• Where the marketplace allows it, grant the key only the permissions it needs.
• On channels such as Etsy and eBay, use one-click authorization; there is no key to copy, and you can revoke access from the marketplace side at any time.
• The marketplace account that issues the key should belong to the company, not a person, so it does not close when that person leaves.
• Rotate keys periodically; after rotation, confirm on the channel monitoring screen that the connection is healthy.
• Keep one list of which key is defined for which channel with which permissions.

The ownership flag is a security tool as well: the product × channel marker that says "is this channel managed by the integration or by an external system?" stops an unauthorized tool from writing to a channel. How the flag is used during setup is described in the shadow mode article.

Rule 4: offboarding, audit trail, and alerts

Staff changes are where security gaps most often appear. Steps to apply the same day:

1. Deactivate the panel account; deactivate rather than delete so the activity history survives.
2. Change any shared passwords the person knew.
3. If the person generated marketplace API keys under their own name, revoke and regenerate them.
4. Remove their phone from notifications and the mobile interface.
5. Review the last thirty days of activity: bulk price changes, CSV exports, channel connection changes.
6. Hand the role to the new owner; assign by job, not by person.

For the audit trail, the panel must record activity by user name. You should be able to answer "who changed the price of which product, and when?" within minutes.

System health and alerts

Security is not only about access; knowing the system is running is security too. A channel that goes quiet is sometimes the sign of a revoked API key. If channel monitoring runs continuously, you notice within minutes rather than on the night of a sale. A system health screen shows whether the problem is on your side, the integrator's, or the marketplace's.

Security checklist

Review every quarter:

• Every user has a personal account; there is no shared account.
• 2FA is on for every user; backup codes are stored.
• Roles follow the job; price writing is limited to two or three people at most.
• The admin account is not used for daily work.
• The API key list is current: which channel, which permissions, when last rotated.
• Marketplace accounts are registered with company email addresses.
• The six-step offboarding list has been applied for anyone who left.
• Activity history is sampled monthly.
• Channel monitoring alerts reach at least one phone.
• The ownership flag is correct for every channel.

The same logic applies to customer-facing areas such as the returns portal and the message inbox: customers reach the returns portal with only an email and an order code, while the staff side is limited by role. See marketplace returns management and the returns portal.

How this works with Bulutegra

In Bulutegra every user signs in with their own account, two-factor authentication can be enabled on every account, and the Admin / Content / Warehouse / Accounting roles come ready to use. One-click authorization for Etsy and eBay, the product × channel ownership flag, channel monitoring continuously, and the system health screen all live in the same panel. To see how to set up permissions for your own team, request a demo or ask for a quote.