> For the complete documentation index, see [llms.txt](https://docs.bdb.ai/administrative-settings-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdb.ai/administrative-settings-1/admin-panel-options/configurations/secret-management.md).
# Secret Management
The ***Secret Management*** setting gives facility to prevent the database-related or any other sensitive/confidential information from getting exposed. In Secret Management Settings the Admin configures the Key of the Sensitive data but the actual value is saved in Kubernetes as Environmental Variable by the DevOps Team.
## Steps to Add Secret Key
* Click on the ***Secret Management*** icon from the Configuration Admin option.
* The ***Secret Management*** page opens.
* Click on the ***New*** option to add a new secret***.***
* Click on the ***Add New Field*** icon for the Secret Management option.
* The option to add ***Secret Key*** will come as shown in the below images.
* Provide the ***Secret Key*** in the given space.
* Click the ***Save*** option.
* A confirmation appears.
* The secret will be saved and displayed in the list as shown below.
* To add a new field click on the + icon provided for the Secret (Mongo) as shown below images.
* Add multiple fields inside this secret like Port, Host, Username, Password, etc depending upon the requirement.
* Once We have added all the required fields, click the ***Save*** option to save all the fields of Secret.
* A confirmation message appears.
{% hint style="info" %}
*Please Note:*
* *Click the **View*** *icon to display all the added fields.*
* *Click the **Delete*** *icon to remove the added Secret key.*
* *Click the **Close*** *icon to remove an added field.*
{% endhint %}
### Steps to Share a Secret Key
Once Admin has configured the settings, it is possible to share it to a user/User Group to use this secret by clicking the ***Share*** icon provided next to the saved Secret Key.
* Click the ***Share*** icon for a saved Secret Key.
* The ***Share Secret Key*** window opens.
* Select the **USER** or **USER GROUP** option to list the users (Use the **EXCLUDE USER** to exclude the user from the right to access a shared Secret Key).
* Select User(s)/User Group(s) from the list.
* Use arrow to move the selected user(s) and user group(s) to the right side box.
* Once the selected user(s) and user group(s) appear in the right side box.
* Click the ***Save*** option.
* A confirmation message appears and the Secret Key gets shared to the selected user(s) or user group(s).
{% hint style="info" %}
Please Note: Once Configuration is done Admin needs to request the DevOps team to add the actual keys in the Kubernetes. The names of the Keys should be in the below format: MONGO\_HOST, MOGO\_PORT , MONGO\_USERNAME , MONGO\_PORT
Once the ***DevOps*** team has been configured the secret key’s value, it can be used in any module. For Reference check out the Secret tab inside the ***Data Science Lab*** Module.
Hence, We can see that the actual value of Mongo-related fields is not exposed anywhere in the platform.
{% endhint %}
*icon to display all the added fields.*
* *Click the **Delete*** 
*icon to remove the added Secret key.*
* *Click the **Close*** 
*icon to remove an added field.*
{% endhint %}
### Steps to Share a Secret Key
Once Admin has configured the settings, it is possible to share it to a user/User Group to use this secret by clicking the ***Share*** 
icon provided next to the saved Secret Key.
* Click the ***Share*** icon for a saved Secret Key.
