From 0d98c09a09a8374151bd8cdbc0c7c0e0a9725f7d Mon Sep 17 00:00:00 2001 From: David Myriel Date: Tue, 18 Jun 2024 04:03:49 -0700 Subject: [PATCH] Update qdrant-landing/content/articles/data-privacy.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Kacper Łukawski --- qdrant-landing/content/articles/data-privacy.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/qdrant-landing/content/articles/data-privacy.md b/qdrant-landing/content/articles/data-privacy.md index f84db8638..bcba3c562 100644 --- a/qdrant-landing/content/articles/data-privacy.md +++ b/qdrant-landing/content/articles/data-privacy.md @@ -190,12 +190,12 @@ As we saw above, JWT claims create powerful levers through which you can create In a typical enterprise application, you will have a segregation of users based on their roles and permissions. These could be: -1. Admin or Owner: with full access, and can generate API keys. -2. Editor: with read-write access levels to specific collections. -3. Viewer: with read-only access to specific collections. -4. Data Scientist or Analyst: with read-only access to specific collections. -5. Developer: with read-write access to development- or testing-specific collections, but limited access to production data. -6. Guest: with limited read-only access to publicly available collections. +1. **Admin or Owner:** with full access, and can generate API keys. +2. **Editor:** with read-write access levels to specific collections. +3. **Viewer:** with read-only access to specific collections. +4. **Data Scientist or Analyst:** with read-only access to specific collections. +5. **Developer:** with read-write access to development- or testing-specific collections, but limited access to production data. +6. **Guest:** with limited read-only access to publicly available collections. In addition, you can create access levels within sections of a collection. In a multi-tenant application, where you have used payload-based partitioning, you can create read-only access for specific user roles for a subset of the collection that belongs to that user.