From e0a48a4d17f9b55420ac4100601b34da3b2c7fb9 Mon Sep 17 00:00:00 2001
From: Elizabeth Vo <65384387+ensvo@users.noreply.github.com>
Date: Thu, 26 Sep 2024 13:13:37 +0900
Subject: [PATCH] add test plan, registries and packages scopes

---
 pages/apis/managing_api_tokens.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/pages/apis/managing_api_tokens.md b/pages/apis/managing_api_tokens.md
index e3a8557dc3..dc864d9fbd 100644
--- a/pages/apis/managing_api_tokens.md
+++ b/pages/apis/managing_api_tokens.md
@@ -30,6 +30,14 @@ REST API scopes are very granular, you can select some or all of the following:
 * Read Suites `read_suites` - Permission to list and retrieve details of test suites; including runs,
   tests, executions, etc.
 * Write Suites `write_suites` - Permission to create, update and delete test suites
+* Read Test Plan `read_test_plan` - Permission to retrieve test plan information
+* Write Test Plan `write_test_plan` - Permission to create test plan
+* Read Registries `read_registries` - Permission to list and retrieve details of registries
+* Write Registries `write_registries` - Permission to create and update registries
+* Delete Registries `delete_registries` - Permission to delete registries
+* Read Packages `read_packages` - Permission to list and retrieve details of packages
+* Write Packages `write_packages` - Permission to create packages
+* Delete Packages `delete_packages` - Permission to delete packages
 
 When creating API access tokens, you can also restrict which network address are allowed to use them, using [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).