From a0eff06127dfe48a169cc0e591cabab9474e5a24 Mon Sep 17 00:00:00 2001
From: Eirik Nygaard <eirik@vespa.ai>
Date: Tue, 7 Apr 2026 13:15:27 +0200
Subject: [PATCH] Expand description to tenant users

---
 en/learn/tenant-apps-instances.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/en/learn/tenant-apps-instances.html b/en/learn/tenant-apps-instances.html
index ece82a57c7..85a952ead6 100644
--- a/en/learn/tenant-apps-instances.html
+++ b/en/learn/tenant-apps-instances.html
@@ -8,7 +8,7 @@
 
 <p>
   When registering for Vespa Cloud, a <em>tenant</em> is created.
-  Tenant is the billable unit, and most often represents an organization.
+  Tenant is the billable unit, and most often represents an organization or a project.
   A tenant has one or more <em>applications</em> with one or more <em>instances</em>:
 </p>
 <img src="/assets/img/tenants-apps-instances.svg" width="280"
@@ -35,6 +35,11 @@
   and is composed of individually sized <em>clusters</em>.
   A cluster is deployed to a set of <em>nodes</em> with <em>resources</em> specified.
 </p>
+<p>
+  One or more user may be a member of the tenant. A user is given roles in the tenant based on their access level.
+  <em>Administrator</em> for tenant level managment like adding new members and updating billing data,
+  <em>Developer</em> for managing applications, and one for <em>read-only</em> access.
+</p>