diff --git a/docs/Configuring-Pantheon/IBFT.md b/docs/Configuring-Pantheon/IBFT.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/Consensus-Protocols/Comparing-PoA.md b/docs/Consensus-Protocols/Comparing-PoA.md
index 227b97e3bd..a826d9c043 100644
--- a/docs/Consensus-Protocols/Comparing-PoA.md
+++ b/docs/Consensus-Protocols/Comparing-PoA.md
@@ -6,6 +6,9 @@ Pantheon implements the Clique and IBFT 2.0 Proof of Authority consensus protoco
 consensus protocols are used when participants are known to each other and there is a level of trust between them. 
 For example, in a permissioned consortium network. 
 
+!!! note 
+    IBFT 2.0 is under development and will be available in v1.0. 
+
 Proof of Authority consensus protocols allow faster block times and have a much greater throughput of transactions 
 than the Ethash Proof of Work consensus protocol used on the Ethereum MainNet. 
 
diff --git a/docs/Consensus-Protocols/IBFT.md b/docs/Consensus-Protocols/IBFT.md
index 245a88f598..cbd6f28cc2 100644
--- a/docs/Consensus-Protocols/IBFT.md
+++ b/docs/Consensus-Protocols/IBFT.md
@@ -6,6 +6,9 @@ description: Pantheon IBFT 2.0 Proof-of-Authority (PoA) consensus protocol imple
 
 # IBFT 2.0
 
+!!! note 
+    IBFT 2.0 is under development and will be available in v1.0. 
+
 Pantheon implements the IBFT 2.0 Proof-of-Authority (PoA) consensus protocol. IBFT 2.0 can be used for private networks. 
 
 In IBFT 2.0 networks, transactions and blocks are validated by approved accounts, known as validators. 
diff --git a/docs/Consensus-Protocols/Overview-Consensus.md b/docs/Consensus-Protocols/Overview-Consensus.md
index 0ca1ac7fd7..d17554ccc3 100644
--- a/docs/Consensus-Protocols/Overview-Consensus.md
+++ b/docs/Consensus-Protocols/Overview-Consensus.md
@@ -11,6 +11,9 @@ Pantheon implements a number of consensus protocols:
   
 * [IBFT 2.0](IBFT.md) (Proof of Authority)
 
+!!! note 
+    IBFT 2.0 is under development and will be available in v1.0. 
+
 The genesis file specifies the consensus protocol for a chain `config`: 
 
 ```json tab="Ethash"
diff --git a/docs/Reference/JSON-RPC-API-Methods.md b/docs/Reference/JSON-RPC-API-Methods.md
index 461f691e86..ada4303f65 100644
--- a/docs/Reference/JSON-RPC-API-Methods.md
+++ b/docs/Reference/JSON-RPC-API-Methods.md
@@ -1928,6 +1928,9 @@ None
 
 ## IBFT 2.0 Methods 
 
+!!! note 
+    IBFT 2.0 is under development and will be available in v1.0. 
+
 ### ibft_discardValidatorVote
 
 Discards a proposal to [add or remove a validator](../Consensus-Protocols/IBFT.md#adding-and-removing-validators) with the specified address. 
diff --git a/docs/Reference/Using-JSON-RPC-API.md b/docs/Reference/Using-JSON-RPC-API.md
index b3748cf722..971ad01cea 100644
--- a/docs/Reference/Using-JSON-RPC-API.md
+++ b/docs/Reference/Using-JSON-RPC-API.md
@@ -76,8 +76,8 @@ The `ETH`, `NET`, `WEB3`, `CLIQUE`, and `IBFT` APIs are enabled by default.
 
 Use the [`--rpc-api` option](Pantheon-CLI-Syntax.md#rpc-api) to enable the `ADMIN`, `DEBUG`, and `MINER` APIs.
 
-!!!note
-    :construction: IBFT is not currently supported. Support for IBFT is in active development. 
+!!! note 
+    IBFT 2.0 and Permissioning are under development and will be available in v1.0. 
 
 ### Block Parameter