From 53f8609e9db9d3629844a9bec5cf4e35e813f217 Mon Sep 17 00:00:00 2001 From: Cameron Pak Date: Fri, 30 Jan 2026 03:39:53 -0600 Subject: [PATCH] Docs: updating copy to reflect bknd's open opt-in philosophy --- docs/content/docs/(documentation)/start.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/docs/(documentation)/start.mdx b/docs/content/docs/(documentation)/start.mdx index 5d49deb..2b8e855 100644 --- a/docs/content/docs/(documentation)/start.mdx +++ b/docs/content/docs/(documentation)/start.mdx @@ -41,7 +41,7 @@ bunx bknd run This will create a local `data.db` SQLite database file in the folder you ran the command and start the bknd web server at http://localhost:1337. -Right now the admin dashboard is not locked down (AKA "guarded"), which means anyone who can access your dashboard will be able to update the configuration and change data in your entities. To prevent unauthorized use, let's put a guard on your bknd instance. +By default, access to the admin dashboard is open and not guarded. This is intentional because bknd uses an opt-in philosophy model to allow for quick prototyping and intentional configuration. To restrict access and prevent unauthorized use, let's enable authentication and guard the dashboard. We will create a user and an admin role. We will then apply the admin role to the user. Then, we can lock down the admin dashboard by enabling the guard, securing access to your bknd app. Let's begin.