How do I set up a private, invite-only page for partners or dealers?
Short answer: For a small, stable group of partners or dealers, a single password shared across the whole group, placed in front of one page or section, is usually the fastest path and genuinely enough: nobody else can get in, and you're not maintaining individual accounts. Once you need to know specifically who logged in, show different partners different prices or documents, or add and remove individual people without changing everyone's password, that's the point to move to real per-account logins through a tool like Netlify Identity, which handles sign-up, login and role-based access without needing a Netlify account for each partner.
You want a page your dealers or partners can reach but the general public can't, and you want to know whether that's a five-minute job or a real build.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
This page may contain affiliate links from which Blur Studio earns commissions.
"Invite-only" covers two genuinely different setups, and picking the wrong one is the most common way this project gets more expensive than it needs to be. One is a locked door with one key that everyone in the group shares. The other is a locked door with a separate key for each person. Which one you actually need depends on what's behind the door, not on how exclusive you want it to sound.
Shared password versus individual accounts
A shared password in front of a page or section keeps the general public and search engines out, full stop. Everyone with the password sees the same content. This is the right call when every partner or dealer should see the exact same price list, the same spec sheets, or the same set of documents, and you don't need to know which specific person looked at what.
Individual accounts matter the moment any of these become true: different partners should see different prices or territories, you need to know exactly who accessed what and when (useful if a price list leaks and you want to know the likely source), or you add and remove people often enough that changing one shared password every time someone leaves becomes a real hassle, not just a minor one.
Setting up the simple version: a password-protected page
- Identify exactly which page or section needs the lock. Protecting your entire site when only one dealer-resources page needs it creates more friction than necessary for everyone else.
- Set a password at the host or platform level for that specific page or path, not just a "please don't share this link" honor system, which stops working the moment the link gets forwarded once. On Netlify, the platform that builds and serves your site from its connected code, this requires the Pro plan or Enterprise; it isn't included on Free or Personal, so factor that into the cost comparison against individual logins.
- Share the password through a channel you actually control (a direct email, not a public group chat), and change it periodically if the dealer list changes.
- Check that the page is genuinely not indexed by search engines, since a password on the page itself doesn't always stop a cached or indexed version from appearing in search results depending on how the block is configured.
This is the whole job for a small, stable dealer list. If that's your situation, stop here. You don't need individual logins, or a full Netlify account set up for each partner, just because "partner portal" sounds more official.
When you actually need real per-account logins
Netlify's Identity feature is the step up from a shared password: sign-up, login, password reset and role assignment for each person using your site, without them needing their own Netlify account, included on Netlify's credit-based plans (Free, Personal, Pro) with no cap on the number of active users. That last point matters if your dealer network runs into dozens or hundreds of accounts, since you're not paying per seat for them to log in. Custom email templates and a login audit log sit on Pro and Enterprise specifically, which is worth knowing if "know exactly who logged in and when" is one of your actual reasons for moving off a shared password.
Setting this up through Netlify's own signup page for real differentiation (dealer A sees dealer A's pricing, dealer B sees dealer B's) means pairing Identity's role system with your own data: a record somewhere that ties each account to the specific prices, territory or documents that account should see. Identity handles who's allowed in; it doesn't automatically know what "their" content is, you still have to build that connection.
What I'd actually tell a distributor or agency
For a distributor with a genuinely small, stable dealer list (think low double digits, rarely changing), I'd push back on building individual logins even if it sounds more professional, because the maintenance cost of a login system for a handful of people who never change rarely pays for itself. The shared-password version, refreshed every few months or whenever someone leaves the network, does the actual job.
The calculation flips once you're running real wholesale pricing tiers, since showing dealer B the pricing you negotiated specifically with dealer A is a genuine business problem, not an inconvenience. At that point, individual accounts with role-based pricing aren't a nice-to-have, they're how you avoid a dealer relationship blowing up over a pricing leak. An agency managing several client-facing resource pages sits in between: a shared password per client (not per agency-wide group) usually threads the needle, since each client only needs access to their own resources, not everyone else's.
A worked example: a regional distributor with fifteen dealers
A regional equipment distributor with fifteen dealers started with a single shared password protecting a page of spec sheets and a general price list, which worked fine for over a year. The arrangement broke down the moment the distributor began offering two of their longest-standing dealers a better volume discount than the rest of the network, since the shared price list could no longer show one true number without either underpricing the new tier or overpricing the better-rate dealers.
Rather than rebuilding the whole page from scratch, the fix was adding Identity-based individual logins specifically for the pricing section while leaving the spec sheets and general resources behind the original shared password, since those genuinely hadn't changed and didn't need the added complexity. Each dealer account got tagged with their actual discount tier, and the pricing page pulled the right numbers based on who was logged in. The spec sheets stayed simple and shared; only the one section that actually needed differentiation got the heavier treatment, which kept the total build smaller than converting the entire dealer area to individual logins would have been.
Common mistakes with invite-only pages
- Building individual logins before confirming they're actually needed. If every dealer genuinely sees the same content, a password gate does the job at a fraction of the setup and maintenance cost.
- Never rotating a shared password after someone leaves the dealer network. A departed dealer who still has the old password can keep accessing pricing or resources indefinitely unless the password actually gets changed.
- Assuming a password block automatically keeps the page out of search engines. Confirm directly how the specific block is configured, since some setups can still leave a page discoverable or partially cached.
How I'd approach this
I always ask one question first: does every single partner or dealer in this group see exactly the same thing? If yes, a password-protected page is the right-sized answer, and I'd tell a client that plainly rather than talk them into a login system they don't need. If the answer is no, because pricing, territory or documents genuinely differ by account, that's where I'd build real per-account access on something like Identity, tied to the actual data that makes each account different. Where this tends to go wrong is building the login system first and figuring out the data model later; I'd always nail down what each account should actually see before writing a single line of authentication code. If you've already got a dealer portal that's half-built or stuck, that's exactly the kind of project I come in and finish.
Questions people ask
Is a shared password secure enough for a dealer page?
For a small, stable group where everyone should see the same content, yes, provided you share the password through a channel you control and change it when the group changes. It stops the general public and search engines getting in, which is usually the actual goal. On Netlify, password protection requires the Pro plan or Enterprise, not Free or Personal, so confirm your plan covers it.
Can I show different dealers different prices with a shared password?
Not with a single shared password, since everyone who has it sees the same page. Showing different accounts different prices or content needs individual logins with roles, which is what a tool like Netlify Identity is for.
Does a password-protected page keep it out of Google?
It should keep the content from being readable without the password, but check specifically whether the page or a cached version can still appear indexed, since that depends on exactly how the block is set up. Don't assume a password alone guarantees it never surfaces in search.
How many dealers can I have before I need real logins instead of a shared password?
There's no fixed number. The real triggers are needing different content per account, needing to know specifically who accessed what, or having a dealer list that changes often enough that updating one shared password every time becomes a genuine burden.
Is Netlify Identity free?
It's included on Netlify's credit-based plans, including Free, with no extra per-user cost and no cap on the number of active accounts. Custom email templates and a login audit log are reserved for Pro and Enterprise.
What's the real cost of individual dealer accounts versus a shared password?
A shared password costs almost nothing beyond occasionally changing it. Individual accounts cost real setup time, since you need both the login system and the data behind it (which prices or documents belong to which account), plus ongoing management as dealers join or leave.