Base44: Role-Based Publishing Permissions for Enterprise Workspaces
Base44Base44 introduced publishing permissions for Enterprise workspaces, allowing workspace owners and admins to control which roles (Owner, Admin, Editor, Guest) can publish apps, what visibility levels are available to each role, and what the default visibility is for new apps. The feature adds governance for teams that need to prevent non-admin members from accidentally publishing internal tools publicly. Admins configure these controls from Workspace Settings, and the feature is currently rolling out to Enterprise users, not yet available to all.
Featured Video
A video we selected to help illustrate this changelog
Sources & Mentions
1 external resource covering this update
Publishing Permissions Come to Base44 Enterprise Workspaces
Base44 has added publishing permissions to its Enterprise workspace offering, giving workspace owners and admins fine-grained control over who can publish apps and at what visibility level. The update landed on May 31, 2026, and addresses a common governance need for teams building internal tools: preventing non-admin members from inadvertently making private apps publicly accessible.
What the Feature Does
Publishing permissions operate through a role-based configuration table in Workspace Settings. Admins can configure three aspects for each role (Owner, Admin, Editor, and Guest) independently:
- Whether that role can publish apps at all
- Which visibility options (Private, Workspace-only, Public) are available to members in that role
- What visibility level is selected by default when they publish
Members who lack publish rights can still build and edit apps freely, they simply cannot push those apps live. This separation allows teams to maintain development velocity while keeping a tighter grip on what reaches external users.
The Owner role retains unrestricted publishing capabilities and cannot have its settings restricted, preserving workspace-level governance authority.
Rollout Status
As noted in Base44's documentation, publishing permissions are not available to all enterprise users yet, the feature is in limited rollout across Enterprise workspaces. Teams interested in access should check their workspace settings or contact Base44 support.
Why It Matters for Teams
For organizations using Base44 to build internal tools, productivity apps, or customer-facing products, the risk of a developer accidentally publishing an in-progress or internal app to public was a real governance gap. Publishing permissions closes that gap without introducing friction into the build process: editors and guests can iterate freely, while only authorized roles can pull the trigger on a live deployment.
This update complements earlier Base44 Enterprise additions, including workspace-only app visibility controls and workspace member management, building out a more complete governance layer for teams operating at scale.