Base44 auth

Role-Based Access Control Not Restricting Pages in Base44

You have configured roles in your Base44 application (such as Admin, Editor, Viewer) but users are still able to access pages and perform actions that should be restricted to specific roles. The role-based access control appears to have no effect.

This is a critical security issue, especially for apps handling sensitive data. You may notice that regular users can access admin dashboards, edit records they should only be able to view, or see navigation items that should be hidden from their role.

The problem can be inconsistent: sometimes access is properly blocked on one page but not on another, or it works in the editor preview but fails in the published app.

Common Causes

  1. Page-level access rules were set but component-level or data-level access rules were not configured
  2. Role names in access rules don't exactly match the role names assigned to users (case sensitivity)
  3. The app relies on hiding UI elements rather than enforcing server-side access checks on the data
  4. A default role assignment is missing, so new users get no role and bypass role checks entirely
  5. Access rules were configured in the editor but not re-published to the live app

How to Fix It

Review your role configuration to ensure role names match exactly between user assignments and page/component access rules. Base44 may treat roles as case-sensitive strings.

Check that you have applied access restrictions at both the page level and the data level. Hiding a navigation link is not enough; the underlying data queries and actions must also be restricted.

Ensure every new user is assigned a default role upon signup. Users without a role may unexpectedly bypass access checks. For complex multi-role setups, consider having an expert audit your access control configuration to prevent security gaps.

Real developers can help you.

Nam Tran Nam Tran 10 years as fullstack developer prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Omar Faruk Omar Faruk As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience. My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture. I played a key role in creating a scalable and maintainable platform to support educators and learners globally. I'm enthusiastic about embracing new challenges and making meaningful contributions. Dor Yaloz Dor Yaloz SW engineer with 6+ years of experience, I worked with React/Node/Python did projects with React+Capacitor.js for ios Supabase expert Victor Denisov Victor Denisov Developer Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups Matthew Jordan Matthew Jordan I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job. Matt Butler Matt Butler Software Engineer @ AWS Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture Richard McSorley Richard McSorley Full-Stack Software Engineer with 8+ years building high-performance applications for enterprise clients. Shipped production systems at Walmart (4,000+ stores), Cigna (20M+ users), and Arkansas Blue Cross. 5 patents in retail/supply chain tech. Currently focused on AI integrations, automation tools, and TypeScript-first architectures.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Why can regular users still see my admin pages in Base44?

You likely need to set access rules at both the page level and the data/component level. Just hiding navigation links doesn't prevent direct URL access.

How do I set up roles correctly in Base44?

Define your roles in the authentication settings, assign a default role for new signups, then apply page-level and data-level access rules using those exact role names.

Related Base44 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help