Add API token permissions list and improve parallelism

Author: RebeccaTamachiro

src/content/docs/secrets-store/access-control.mdx

@@ -15,12 +15,13 @@ Refer to the list below for default role definitions.
 
 - **Super Administrator**: Can create, edit, duplicate, delete, and view secrets metadata. Can also [add a Secrets Store binding to a Worker](/secrets-store/integrations/workers/).
 - **Secrets Store Admin**: Can create, edit, duplicate, delete, and view secrets metadata. Can also [add a Secrets Store binding to a Worker](/secrets-store/integrations/workers/).
-- (TBC)**Secrets Store Reporter**: Can view secrets metadata but cannot create, edit, duplicate, nor delete secrets.
 - (TBC)**Secrets Store Deployer**: Can view secrets metadata but cannot create, edit, duplicate, nor delete secrets. Can also [add a Secrets Store binding to a Worker](/secrets-store/integrations/workers/).
+- (TBC)**Secrets Store Reporter**: Can view secrets metadata. Cannot perform any actions (create, edit, duplicate, delete secrets), nor add a Secrets Store binding to a Worker.
 
 ## API token permissions
 
-(TBC)
-The following API token permissions can also be used to grant access to Secrets Store resources.
+(TBC) The following API token permissions can also be used to grant access to Secrets Store resources.
 
-- *Account - Secrets Store - Read*:
+- *Account - Secrets Store - Edit*: Allows a user to create, edit, duplicate, or delete secrets.
+- *Account - Secrets Store - Deploy*: Allows a user to view secrets metadata and add a Secrets Store binding to a Worker.
+- *Account - Secrets Store - Read*: Allows a user to view secrets metadata.