diff --git a/docs/Concepts/Permissioning/Onchain-Permissioning.md b/docs/Concepts/Permissioning/Onchain-Permissioning.md
index 5fffd0e0322..a2cf8ab6f8c 100644
--- a/docs/Concepts/Permissioning/Onchain-Permissioning.md
+++ b/docs/Concepts/Permissioning/Onchain-Permissioning.md
@@ -24,10 +24,6 @@ Node Rules and Account Rules contracts. The Ingress contracts are deployed to st
 * Admin - stores the list of admin accounts and admin list operations (for example, add and remove). There is 
 one list of admin accounts for node and accounts.
 
-!!! note
-    The permissioning smart contracts are currently in the process of going through a third party audit. 
-    Please [contact us](https://pegasys.tech/contact/) before using in a production environment.
-
 ## Permissioning Management Dapp
 
 The [Permissioning Management Dapp](../../Tutorials/Permissioning/Getting-Started-Onchain-Permissioning.md) is provided to view 
@@ -47,6 +43,13 @@ Permissioning implements three whitelists:
 
 * Admins are accounts that can update the accounts and nodes whitelists 
 
+!!! caution "Using account permissioning and privacy"
+    Account permissioning cannot be used with [random key signing](../../HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md)
+    for [privacy marker transactions](../Privacy/Private-Transaction-Processing.md).
+    
+    If using account permissioning and privacy, a signing key must be specified using the [`--privacy-marker-transaction-signing-key-file`](../../Reference/CLI/CLI-Syntax.md#privacy-marker-transaction-signing-key-file)
+    command line option and the signing key included in the accounts whitelist.  
+
 ## Bootnodes
 
 When a node is added to the network, it connects to the bootnodes until it synchronizes to the chain head regardless of
diff --git a/docs/HowTo/Limit-Access/Local-Permissioning.md b/docs/HowTo/Limit-Access/Local-Permissioning.md
index c77e686199d..1e394b569f1 100644
--- a/docs/HowTo/Limit-Access/Local-Permissioning.md
+++ b/docs/HowTo/Limit-Access/Local-Permissioning.md
@@ -76,6 +76,13 @@ A node with account permissioning accepts transactions only from accounts in the
     
 Account whitelisting is at the node level. That is, each node in the network has a [permisssions configuration file](#permissions-configuration-file)
 in the [data directory](../../Reference/CLI/CLI-Syntax.md#data-path) for the node.    
+
+!!! caution "Using account permissioning and privacy"
+    Account permissioning cannot be used with [random key signing](../Use-Privacy/Sign-Privacy-Marker-Transactions.md)
+    for [privacy marker transactions](../../Concepts/Privacy/Private-Transaction-Processing.md).
+    
+    If using account permissioning and privacy, a signing key must be specified using the [`--privacy-marker-transaction-signing-key-file`](../../Reference/CLI/CLI-Syntax.md#privacy-marker-transaction-signing-key-file)
+    command line option and the signing key included in the accounts whitelist. 
     
 Transactions are validated against the accounts whitelist at the following points: 
 
diff --git a/docs/HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md b/docs/HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md
index ba548ce922e..e325943e19d 100644
--- a/docs/HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md
+++ b/docs/HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md
@@ -5,10 +5,17 @@ description: How to sign a Privacy Marker Transaction with Hyperledger Besu
 
 Privacy Marker Transactions are signed with a random or specified key. To sign Privacy Marker Transactions with a specified private key, use [`--privacy-marker-transaction-signing-key-file`](../../Reference/CLI/CLI-Syntax.md#privacy-marker-transaction-signing-key-file) when starting Hyperledger Besu.
 
-!!! important
-    You must specify a key in networks where gas is paid, and the associated account must contain adequate funds.
+You must specify a key in networks where gas is paid, and the associated account must contain adequate funds.
     
 In [free gas networks](../../HowTo/Configure/FreeGas.md), exclude the `--privacy-marker-transaction-signing-key-file` command line option to sign each Privacy Marker Transaction with a different random key to add additional anonymity.
 
+!!! caution "Using account permissioning and privacy"
+    [Account permissioning](../../Concepts/Permissioning/Permissioning-Overview.md#account-permissioning) 
+    cannot be used with random key signing.
+    
+    If using account permissioning and privacy, a signing key must be specified using the [`--privacy-marker-transaction-signing-key-file`](../../Reference/CLI/CLI-Syntax.md#privacy-marker-transaction-signing-key-file)
+    command line option and the signing key included in the accounts whitelist. 
+
 !!! note
-    During the [private transaction process](../../Concepts/Privacy/Private-Transaction-Processing.md), Privacy Marker Transactions are signed in Hyperledger Besu.
\ No newline at end of file
+    During the [private transaction process](../../Concepts/Privacy/Private-Transaction-Processing.md), Privacy Marker Transactions are signed in Hyperledger Besu.
+    
diff --git a/docs/Reference/CLI/CLI-Syntax.md b/docs/Reference/CLI/CLI-Syntax.md
index 13ac0a1f89c..ab58643d1a0 100644
--- a/docs/Reference/CLI/CLI-Syntax.md
+++ b/docs/Reference/CLI/CLI-Syntax.md
@@ -984,6 +984,9 @@ privacy-marker-transaction-signing-key-file="/home/me/me_node/myPrivateKey"
 
 `<FILE>` is the name of the private key file used to [sign Privacy Marker Transactions](../../HowTo/Use-Privacy/Sign-Privacy-Marker-Transactions.md). If this option isn't specified, each transaction is signed with a different randomly generated key.
 
+If using [account permissioning](../../Concepts/Permissioning/Permissioning-Overview.md#account-permissioning) 
+and privacy, a private key file must be specified and the signing key included in the accounts whitelist.  
+
 ### privacy-precompiled-address
 
 ```bash tab="Syntax"