One Account Per Rep or a Shared Store Account: How to Choose

A used-car manager handed the floor a single Facebook login and called it the store account. It felt clean. One inbox. One Marketplace presence. One password on a sticky note in the tower. By Thursday three reps had posted from that login on three different browsers, a fourth had reset the password after a lockout, and a fifth was still answering Saturday messages from his personal phone because nobody else could get in.

Shared store accounts feel simpler on a whiteboard. On a live floor they concentrate risk: session collisions, password churn, untraceable posts, and a behavioral fingerprint that does not look like one person selling cars. One account per rep creates its own problems: more logins to document, more warming-up, more places a listing can go stale. The choice is not ideological. It is an operating model.

This article is a decision framework for general managers and internet directors who need to pick one account per rep or a shared store account and then live with the consequences. It is not a Meta policy recitation. Meta does not publish a dealership-approved account architecture. Treat the guidance below as a conservative operating standard and confirm current Marketplace and commerce rules yourself.

Why the Shared Store Account Breaks First

The shared model survives only while one person actually uses it. The moment two people post, the account stops matching a human pattern and the store loses the ability to say who did what.

What "shared" usually looks like in practice

• One personal profile that "belongs to the store," logged in on the front desk PC, a manager laptop, and two phones.
• A Business Page that everyone posts from, with Marketplace activity mixed in from whoever is logged in that hour.
• A rotating password sent in a group text whenever someone gets locked out.

Each of those is a different failure. The first looks like a compromised personal account. The second blurs Page and personal identity. The third guarantees that former employees still have access.

The operational costs you will actually feel

• No owner for a bad listing. A wrong price or a mismatched photo cannot be traced to a person, so it cannot be coached.
• Inbox contention. Two reps reply to the same buyer. Or nobody replies because everyone assumes someone else has it.
• Session fights. Logging in from a new device kicks someone else out mid-post.
• Offboarding failure. When a rep leaves, you cannot recover the account without changing a password that the whole floor uses, which takes everyone offline at once.

If your current pain is "we cannot tell who posted the Camry," you already have the answer. A shared store account cannot support accountability.

When One Account Per Rep Is the Better Default

For most dealerships with more than one person posting, one account per rep is the cleaner default. Each salesperson or associate posts from a Facebook identity they actually use, at a pace that can look like a person, with a queue they own.

What one-account-per-rep requires of the store

It is not "let everyone post from their personal Facebook and hope." It is a controlled map:

• Named people, named accounts, named inventory slices.
• A written rule that nobody else logs into that account.
• A warm-up plan for any account that is new to Marketplace. See warming up a new Facebook account before posting inventory.
• A roster so managers know which login exists, who holds it, and what it is allowed to post.

Benefits you can run a desk on

• Pacing stays human. One person, one cadence, irregular gaps that match a real workday.
• Coaching is possible. Posting analytics and lead response can be discussed with a name attached.
• Offboarding is a unit problem, not a store outage. You reassign that rep's live listings. You do not reset the whole floor.
• Device hygiene improves. A rep's phone and one Chrome profile beat five people on the tower PC.

The cost is administrative: more accounts to document, more inventory assignment, and more discipline about duplicates. That cost is cheaper than a single shared login that everyone treats as a public terminal.

When a Limited Shared Presence Still Makes Sense

A shared identity is not always wrong. It is wrong as the only posting login for a multi-rep floor. It can still have a narrow job.

A store-level presence for brand, not for volume posting

Some independent lots want a single Marketplace "face" that customers recognize: the lot name, the lot address, the lot phone. That can be one carefully controlled account or Page used by one named operator (often the owner, the internet director, or one manager), not by the whole sales team.

Rules that keep that presence from collapsing into a shared password:

• One human is the operator. A backup is documented, not a group text.
• Floor reps do not post from it. They post from their own accounts, or they do not post.
• Password and recovery email live in a manager-only vault, not on the monitor bezel.
• The account is never used from random networks or from a rep's personal laptop on the drive home.

Solo sellers and tiny lots

A one-person independent lot should not manufacture extra accounts. One login, one operator, one inventory. The Starter-shaped operation (a single seller, a single daily cadence) is the case where "shared store account" and "one account per rep" are the same thing.

What not to share even then

Do not share:

• A manager's personal profile that also holds family photos.
• An account that was warmed up under one person's identity and is now used by whoever is on duty.
• Credentials with seasonal hires, detailers, or anyone whose job does not include posting.

For how roles should map once you leave Facebook and enter the posting tool, see admin, manager, sales rep, and associate roles.

One Account Per Rep or a Shared Store Account: A Decision Framework

Do not vote by preference. Score the store against a few operating facts.

Ask these questions

1. How many people post in a normal week? One: shared and personal are the same. Two or more: default to one account per rep.
2. Do you already fight over the inbox? Shared will make that worse.
3. Can you name, today, which Facebook login posted each live unit? If no, shared has already failed.
4. What happens Friday at 5 when a rep quits? If the answer is "we change the store password and hope," you need per-rep accounts plus an offboarding checklist.
5. Are you a multi-lot or franchise rooftop? Shared across lots is how you post the same VIN in two cities. Keep accounts and inventory tied to a rooftop.

A simple recommendation table

Implementation sequence if you are migrating off a shared login

1. Freeze new posts on the shared account except for the named operator.
2. Document every live listing: VIN, price, who thinks they own it.
3. Stand up per-rep accounts with a conservative warm-up, not a forty-unit dump on day one.
4. Assign inventory so two accounts never hold the same VIN.
5. Move sold-unit cleanup onto every account the same day a deal pencils.
6. Retire the shared login for posting, or restrict it to the single operator model above.

Do not "catch up" by blasting the backlog through new accounts. That recreates the burst-posting pattern a shared login already trained into the team. Pair the account model with the inventory assignment rules in how to assign inventory to floor reps.

How PostToMarket Automates This

Choosing one account per rep only works if the posting tool also refuses to treat the floor as one shared login. PostToMarket is built so each person signs in as themselves, works a queue they own, and posts one vehicle at a time instead of passing around a store password. It is an independent tool, not affiliated with or endorsed by Meta, and it cannot make Facebook treat any account architecture as approved.

Identity that matches the floor

• Sign in to the Chrome extension with email. No API keys, no shared token sitting in a browser.
• Roles are admin, manager, sales rep, and sales associate. The Dealership plan supports up to 13 team logins and 2 managers, so the Facebook map and the product map can line up.
• Associates receive assigned queues. Sales reps self-queue from shared inventory. Managers are not forced to hand a Facebook password to a junior hire.

Pacing that does not depend on who grabbed the tower PC

• One vehicle at a time, with human-like delays.
• Server-enforced daily post limits and delays, so a shared "catch-up Friday" cannot override the rules.
• Unlimited vehicles in inventory on every plan, which removes the temptation to park overflow on a communal account.

Visibility when something goes wrong

• Inventory statuses (draft, posting, posted, sold, failed) show state without asking who is logged into Facebook.
• Team queue view lets a manager release a claim if a rep is out.
• Posting analytics by rep and source, plus a leads inbox, give managers a name to coach instead of a shared inbox to argue over.

The product does not replace your Facebook account decisions. It makes a per-rep model operable.

Pick an Account Model Before the Next Hire Starts Posting

One account per rep or a shared store account is not a branding debate. It is whether your Marketplace operation can survive a lockout, a resignation, and a Saturday of overlapping replies. Most floors with more than one poster should stop sharing the store login and put each person on an account they alone use.

PostToMarket supports that model with email sign-in, per-rep queues, manager assignment for associates, and AutoPost that paces listings like a disciplined human. A solo operator can run Starter at $59 per month with one login. A team that has outgrown the sticky-note password should look at Dealership at $299 per month for up to 13 logins.

Start a 10-day free trial through secure Stripe checkout. Map your people to logins, assign the first queues, and retire the shared account as a posting tool. Cancel anytime.