From 0f39397778e2e7e7a0b801f91991a8434a59d0a1 Mon Sep 17 00:00:00 2001 From: omer-topal Date: Fri, 20 Feb 2026 12:11:35 +0300 Subject: [PATCH] docs: add naming conventions for entities --- docs/getting-started/modeling.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/modeling.mdx b/docs/getting-started/modeling.mdx index 8b042a0dc..2d504b494 100644 --- a/docs/getting-started/modeling.mdx +++ b/docs/getting-started/modeling.mdx @@ -60,7 +60,9 @@ The first step to building Permify Schema is creating entities. An entity is an Think of entities as tables in your database. It is strongly recommended to name entities the same as the corresponding database table name. Doing so allows you to model and reason about your authorization and eliminate the possibility of error. -You can create entities using the `entity` keyword. Let's create some entities for our example GitHub authorization logic. +You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long. + +Let's create some entities for our example GitHub authorization logic. ```perm entity user {}