From 414aef6f1a8d166c4c1276ed4bfcd6e5999dfa16 Mon Sep 17 00:00:00 2001 From: Pratik <10096516+pratikgajjar@users.noreply.github.com> Date: Fri, 18 Sep 2026 16:53:17 -0700 Subject: [PATCH] docs(profiles): drop the sidebar icon and the plan table MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review feedback from Rudraj on the docs preview. The sidebar icon made Profiles the only entry in platform/features with one; every sibling page has no icon, so it read as a rendering accident. The plan table stated Pro/Enterprise availability, which is not how the feature is reaching customers: it is enabled per organization on request while in beta. A table naming tiers invites a self-serve upgrade that does not turn it on. Keeps the two conditions that are not about pricing — schema configured and an entity-scoped memory — and the note that a disabled project reads back not_enabled rather than erroring. --- docs/platform/features/user-profiles.mdx | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/docs/platform/features/user-profiles.mdx b/docs/platform/features/user-profiles.mdx index 4575784b5..793f745b3 100644 --- a/docs/platform/features/user-profiles.mdx +++ b/docs/platform/features/user-profiles.mdx @@ -1,7 +1,6 @@ --- title: Profiles description: "Build a structured, always-current summary of each user from their memories, shaped by a JSON Schema you define." -icon: "id-card" --- # Profiles @@ -17,7 +16,10 @@ Search answers "what did this user say about X". A profile answers "who is this - You want the same fields for every user, so your code can rely on their shape. -Profiles are a **Pro-plan feature** — see [Plan availability](#plan-availability) for the details. + + User Profiles are in **beta** and available on request. To enable them for your + organization, contact [support@mem0.ai](mailto:support@mem0.ai). + ## How it works @@ -261,16 +263,12 @@ else: A schema has a size budget of roughly **10,000 tokens** of serialized JSON — the whole schema is sent to the model on every generation, so a handful of verbose fields can cost more than many terse ones. Oversized schemas are rejected on save. -## Plan availability +## Availability -| Capability | Free | Starter | Pro | Enterprise | -|---|:---:|:---:|:---:|:---:| -| **Profiles** (define a schema, generate, read) | — | — | ✓ | ✓ | -| **Profiles dashboard** (schema editor, samples) | — | — | ✓ | ✓ | +The feature is in beta and enabled per organization on request — see the note at the top of this page. -Profiles require a **Pro plan or higher**. For an individual entity to get a profile, three things must hold: +Once it is on, an entity gets a profile when two more things hold: -- the project is on **Pro or above**, - profiles are **enabled** with a schema for the project (see [Define the schema](#define-the-schema)), and - the memory is scoped to an entity — a `user_id`.