Signing Into the PostToMarket Extension With Email: No API Keys

A common IT conversation at a dealership goes like this. Someone asks how a new tool connects. The vendor replies with a long string of characters to be pasted into a settings field. That string gets saved in a text file, texted to a rep, and eventually lives in three places nobody can account for. Months later, a rep leaves the store and the key is still in circulation.

PostToMarket takes a simpler approach for the Chrome extension: you sign in with your email. There are no API keys to generate, copy, store, or rotate. A rep installs the extension, signs in with the account that belongs to them, and starts working their queue.

This article explains what email sign-in means in practice for general managers, internet directors, and floor reps. It covers the rollout steps, habits that keep accounts clean, why shared logins are a bad idea, and what to do when someone leaves. It does not describe internal security architecture, and it does not promise any particular security outcome. PostToMarket is an independent tool, not affiliated with, endorsed by, or sponsored by Meta. For help with account issues, email info@posttomarket.com.

What "No API Keys" Means for Your Team

Fewer secrets to manage

An API key is a credential that sits outside the normal sign-in experience. It tends to get shared, stored insecurely, and forgotten. Removing the need for one eliminates a category of housekeeping and a category of risk. Reps do not need to know what an API key is, and managers do not need to track who has one.

Access follows the person

When each person signs in with their own email, the extension's activity belongs to that person. That matters for your queue and your accountability: you can tell who is working which units, and you can see posting analytics by rep and source.

Email sign-in is not the same as your Facebook login

Two separate things are happening in the browser. You sign into the PostToMarket extension with your PostToMarket email. Separately, the browser is signed into Facebook with the profile that will be used for posting. Keep those straight in training. The extension posts through the Facebook account that is signed in on that browser, so each rep should be signed into their own Facebook account. Do not hand a Facebook password to a coworker to make posting convenient.

Rolling Out Extension Sign-In to a Team

A smooth rollout takes a short, repeatable checklist.

Admin setup

1. Create your account and choose a plan. The admin account is the primary login for the dealership.
2. Add team members. On the Dealership plan, you can have up to 13 team logins, with roles for admin, manager, sales rep, and sales associate. Starter is a solo account with one login.
3. Assign roles deliberately. Managers can handle team and settings, sales reps self-queue from shared inventory, and associates work from queues that managers assign.

Each rep's first-day steps

1. Install the Chrome extension in the browser the rep uses for work.
2. Sign in with their own email.
3. Confirm the browser's Facebook session is the rep's own and is the account they intend to post from.
4. Open their queue and post a first unit with the manager watching.
5. Check the status of that unit. It should move through draft, posting, and posted, or land in failed if something needs attention.

A thirty-minute training agenda

• Five minutes: how queues and roles work.
• Five minutes: sign-in, and why each person uses their own account.
• Ten minutes: post a real unit together.
• Five minutes: what the statuses mean. See PostToMarket Inventory Statuses Explained.
• Five minutes: who to ask when something goes wrong.

For a longer rollout plan, the walkthrough in PostToMarket Chrome Extension Setup Guide for Dealership Teams goes step by step.

Habits That Keep Accounts Clean

Email sign-in is simple, but the habits around it still matter.

One person, one login

Sharing a login across reps defeats queues, analytics, and accountability. It also makes it impossible to know who did what when something goes wrong. If you need more people, add more users within your plan instead of sharing.

Use a work email that the store controls

Where possible, give reps a store-managed email address, not a personal one that leaves with them. That makes handover and offboarding cleaner, and gives managers a reliable record of who has access.

Protect the email account itself

Your PostToMarket sign-in is only as safe as the email behind it. Use a strong, unique password and turn on the additional sign-in protections your email provider offers. Remind reps never to share verification codes or passwords, including with people who claim to be from support. If you need help with your account, write to info@posttomarket.com.

Sign out on shared machines

If a computer is shared between shifts, make signing out part of the end-of-shift routine. Better still, give each rep their own browser profile on a shared machine, so extension sessions and Facebook sessions are never mixed. Mixed sessions are also how posts end up on the wrong profile, which ties into the guidance in Setting Policy for Reps Who Post Inventory From Personal Profiles.

Offboarding and Role Changes

People leave, change roles, and get promoted. The sign-in process should handle all three without drama.

When a rep leaves

• Remove their access the same day.
• Review their queue and release any claimed units. The team queue view lets managers see and release any claim.
• Reassign units to another rep or associate.
• Mark sold units that were left unresolved.
• Make sure the rep's Facebook session is removed from any store-owned device.

When roles change

When someone moves from associate to sales rep, or sales rep to manager, update their role so their access matches their responsibilities. Remember the structure: the dealership admin is the primary login, managers handle team and settings, and associates are limited to their queue.

A quarterly access review

Once a quarter, a manager should list every active login and confirm each belongs to a current employee in the right role. It takes ten minutes and prevents the most common access problems.

How PostToMarket Automates This

Email sign-in is one small part of a posting workflow designed to be operated by real people on a real sales floor.

Simple access

• Sign in to the Chrome extension with email, with no API keys.
• Roles for admin, manager, sales rep, and sales associate, with up to 13 team logins on the Dealership plan and one login on Starter.

Controlled posting

• One vehicle at a time, with human-like delays, and server-enforced daily post limits and delays so pacing is consistent across the team.
• Posting to Marketplace, your Facebook profile, and Facebook groups through the same extension.
• Personal and per-rep queues, manager assignment, and a team queue view for release and reassignment.

Clean inventory behind it

• Bulk CSV and Excel import with import history and a row-level error log.
• AI-generated titles and descriptions, editable before posting, and a Facebook photo picker.
• Inventory statuses (draft, posting, posted, sold, failed) and mark as sold and archive, with unlimited vehicles on every plan.

No tool can guarantee that Facebook will distribute every listing. PostToMarket reduces the operational mistakes that commonly cause problems; it does not remove the need to follow Meta's current commerce policies and Marketplace rules.

Get Your Team Signed In and Posting: Start Your 10-Day Free Trial

No API keys, no secret strings in a text file, and no mystery about who is posting what. Install the extension, sign in with email, and your team can be working queues the same day.

The Starter plan is $59 per month for a solo seller or independent lot with one login. The Dealership plan is $299 per month for up to 13 team logins and two managers. Start your 10-day free trial with secure Stripe checkout, sign in to the extension with your email, and post your first unit. Cancel anytime.