How to Restrict a Membership Dashboard to Logged-In Users in Framer

• A membership dashboard is a private page: only logged-in members can see it, unlike the rest of your site.
• Framer builds the layout, the same way it builds any other page. Auth Plugin controls who's allowed to see it.
• Protect it with Protected Pages, not by hiding the nav link. A hidden link still leaves the page wide open to anyone with the URL.
• Personalize it with the member's own name, avatar, and profile data automatically, no manual setup per user.

A membership dashboard is the page a logged-in member lands on after sign-in: their profile, their content, their account. This guide covers building that page in Framer, locking it to logged-in users, and filling it with the visitor's own data, no backend code involved.

It's the private home page a member sees after they log in, not a public page anyone can browse to. Search the term and you'll mostly find something else: admin tools that track member counts, renewal dates, and engagement stats for the site owner, not the member. That's a different page for a different audience.

Auth Plugin itself has both. There's a user management dashboard where you, the site owner, view identities and activity. This guide is not about that one. It's about the page your member sees.

Getting this distinction right matters before you build anything. If you go looking for "dashboard" inspiration and land on an admin analytics tool, you'll end up designing the wrong page: charts and metrics instead of a welcoming, personal home base for one visitor.

Here's the short version of how a member dashboard differs from a normal public page on your site:

No. Auth Plugin has no dashboard-builder or layout component. You build the page with Framer's normal layout tools, same as any other page on your site.

What Auth Plugin adds are two things: it stops logged-out visitors from loading the page at all, and it fills the page with the visitor's own name, email, and photo automatically. The layout, the sections, the design decisions are yours.

No. A lot of Framer builders start by just removing the dashboard link from the visible menu for logged-out visitors. Anyone who guesses or bookmarks the URL still loads the page in full.

This is a well-documented mistake outside Framer too. The OWASP guidance on this is blunt: client-side checks are fine for user experience, but they should never be the thing actually deciding who gets in, because they're trivial to bypass. Hiding a button doesn't block the page behind it.

Protected Pages blocks the page at the network level instead of the menu level. Add your dashboard URL as a protected pattern (something like /dashboard.* covers the page and any subpages under it), and a logged-out visitor gets redirected to sign-in before your dashboard content ever renders. There's nothing to hide because there's nothing sent to their browser.

Setup steps:

1. Open Protected Pages in your Auth Plugin settings.
2. Add the dashboard URL pattern.
3. Set the redirect destination (your sign-in page).
4. Test it in an incognito window. If you can see the dashboard while logged out, the pattern's wrong.

That last step matters more than people think. Test logged out, every time you change a pattern. Our role-based access guide covers the full pattern syntax and how the underlying redirect works, plus how to layer role-specific rules with Advanced Access Control on the Pro plan if you eventually need different dashboard views per membership tier.

Two details worth getting right on day one. First, set the redirect to send people back to the dashboard after they sign in, not to your homepage. Losing that destination is a small thing that quietly annoys returning members. Second, if your dashboard has sub-pages (a separate billing tab, a separate settings tab), use the wildcard pattern so you're not adding a new rule every time you add a tab. /dashboard.* catches /dashboard/billing and /dashboard/settings automatically.

No, they won't get randomly logged out while active. The Relay Script keeps the session token fresh in the background and refreshes it automatically while the tab is open, so a member actively using the dashboard stays signed in. You don't need to build any of this yourself. It comes with Protected Pages.

If the session does lapse (a long-idle tab, a manually revoked token), the next protected action redirects them to sign in again, the same as a first-time visit.

Once the page is locked down, the second half of the job is making it feel like it belongs to the person looking at it. Three components handle this.

Identity Label drops the visitor's name or email straight into a text layer. Use it for the "Welcome back, [name]" header at the top of the dashboard.

Avatar Component shows their profile photo, or their initials on a colored background if they haven't uploaded one. Drop it next to the Identity Label and the header already feels personal with zero manual work.

Profile Form auto-populates with the user's current data and lets them edit their name and email with validation built in. Put this on an account settings section of the dashboard, not the main view, so the landing page stays focused.

If you already have text layers built with Framer's own typography and don't want to swap in a new component, the Auth Plugin Overrides apply the same live data to your existing elements instead. Full details on all of these, including hover-to-upload photo behavior, are in our branding and profiles guide.

Keep it to what a solo builder can realistically maintain. Split it into three tiers instead of one long list.

Must-have:

• A personalized greeting (name and photo)
• A way to sign out
• Access to the member's own account details

Nice-to-have:

• Quick links to the two or three things members do most
• A short "start here" section for new members
• Easy access to support

Optional:

• Plan-specific content or upgrade prompts
• Community elements: simple stats or recognition for active members
• A "member since" date or similar personal touch

That must-have/nice-to-have split matches the consistent short list across well-designed member areas, per MemberDev's research: a personalized greeting, curated quick links, and easy support access, kept tight rather than sprawling. Across membership sites generally, a dashboard that tries to surface everything a member could possibly want tends to bury the few things they actually came for. Simpler, more focused dashboards are the better default, and you can always add sections later once you know what members actually click.

Chris Lema's dashboard breakdown adds the account-management side: a place to see and update billing details, past access or downloads, and profile info, all in one spot instead of scattered across separate pages. He frames it as reducing "involuntary churn," the kind that happens when a card expires and nobody notices until it's too late.

Here's how that maps to a layout in Framer, greeting up top, actions in the middle, account details lower down:

------------------------------------------------
|  [Avatar]  Welcome back, {Identity Label}      |
------------------------------------------------
|  [Quick link]   [Quick link]   [Quick link]    |
------------------------------------------------
|  Upgrade prompt (Access Switch, free users)    |
------------------------------------------------
|  Profile Form: name / email / photo            |
------------------------------------------------
|  [Sign Out Button]                             |
------------------------------------------------

This is a rough block sketch of where each piece goes, not a screenshot. The exact styling is yours to design in Framer. Mapped to Auth Plugin components: Identity Label plus Avatar Component for the greeting, a Stack of buttons for quick links, an Access Switch to show or hide the upgrade prompt by plan tier, a Profile Form for account details, and a Sign Out Button that stays visible instead of buried in a menu.

That's a complete, working Framer member dashboard, personal from the moment it loads, built on a straightforward user profile dashboard layout without touching a line of backend code.

A handful of setup mistakes show up over and over on member dashboards:

• Hiding the nav link instead of protecting the page. Covered above: a hidden link is not a locked door. Use Protected Pages, not menu tricks.
• Forgetting the wildcard for sub-pages. /dashboard alone won't cover /dashboard/billing. Use /dashboard.* so every sub-page under it is covered automatically.
• Never testing logged-out access. Every time you change a Protected Pages pattern, open an incognito window and confirm you're actually blocked. Skipping this is how pages end up quietly unprotected.
• Overloading the dashboard with too many links. A dashboard that tries to be the whole site's nav menu buries the two or three things members actually came for.
• Putting profile editing on the main view. Name, email, and photo editing belongs in a settings section, not the first thing a member sees when they land.

No, and you shouldn't try to force it. Google's gated content guidance is mainly written for publishers gating articles behind a paywall who still want those articles findable. A member dashboard isn't that. It's an account utility page, not a piece of content someone should land on from a search result.

With Protected Pages in place, Googlebot gets redirected the same as any logged-out visitor, so the page effectively won't get indexed on its own. That's the correct outcome. Leave it out of your sitemap and don't worry about it. Your energy is better spent making sure the pages you do want ranked, your homepage, your pricing page, your public blog posts, are the ones getting crawled.

Can I protect multiple dashboard pages?
Yes. Protected Pages isn't limited to one URL. Add a pattern for each section you want gated, or one wildcard pattern that covers a whole group of sub-pages at once.

Can members bookmark the dashboard?
Yes. Protected Pages checks auth state whenever the page is requested, bookmark, direct link, or nav click included. A logged-in member's bookmark loads the dashboard normally; a logged-out visitor with the same bookmark gets redirected to sign-in.

Can I show different dashboards per plan tier?
Yes, using Advanced Access Control on the Pro or Scale plan for role-specific rules, combined with Access Switch inside the page to show or hide sections by tier.

Can I customize the post-login redirect?
Yes. Point it at your dashboard URL, or wherever makes sense for your site, instead of leaving it on a generic default.

Can I use CMS content inside a protected dashboard?
Yes. Framer CMS collections work the same on a protected page as anywhere else. Protection happens before the page renders; the CMS content behaves normally once a member is in.

Does a protected dashboard affect SEO?
No, in the sense that matters. As covered above, it won't get indexed, and it shouldn't. It's an account page, not a page you want ranking.

Building this page comes down to three moves: build the layout in Framer like any other page, protect it with Protected Pages instead of a hidden nav link, and personalize it with Identity Label, Avatar Component, and Profile Form. From there, expanding into a full membership site (paywalled content, a sign-up flow, gated pages across the whole site) is the natural next step, not a separate system.

If you're setting up a membership site from scratch, paywall and all, that's a bigger project than this guide covers. Our membership site walkthrough goes through the full build, including where the dashboard fits into gated pages, sign-up flow, and content access as a whole. This guide is the deeper version of just that one piece, whether you're adding it to a membership site you're building today or fixing one you already shipped with just a hidden nav link standing in for real security.

Protected Pages, every one of the 13 components used above, and custom branding are all included on the free Auth Plugin plan, up to 100 identities on one site. Nothing in this guide needs an upgrade. If you outgrow the free tier's identity limit, the Pro and Scale plans carry the same components forward, just with more identities, more sites, and the Advanced Access Control mentioned earlier for role-specific dashboard views.