#2500-#2136-Encrypt & Mask AI Key on Dashboard- Urgent

The Dreamaholics 11 hours ago

Hello Team,

We would like to report an important product and security requirement we have observed while working with AI-enabled bots on the platform.

Observation

In the attached video, we observed the following behavior:

When Bot AI Agent and Bot AI Assistant are turned OFF, the AI Training section becomes invisible to the end user.However, AI responses continue to function correctly in the background, which confirms that the AI system can run without exposing the AI Training UI to the user.

This behavior indicates that AI visibility and AI functionality are already technically separable.

Problem / Risk

Currently:

End users can see AI Integration settings, AI Training, model selection, and API key fields.API keys and AI configuration details are visible or inferable from the dashboard.This creates:Security risks (API key exposure / misuse)Unnecessary confusion for non-technical usersLack of control for SaaS owners/resellers who want to manage AI centrally
What We Require (Feature Request)

We request a dedicated feature or toggle that allows us to:

Completely hide or disable the AI Integration & AI Training sections from the end-user dashboardEnsure that:AI continues to function seamlessly in the backendEnd users cannot view, access, or modify AI training, prompts, models, or API keysThis control should be account-level or role-based, so platform owners/resellers can decide:Whether AI is user-managed or system-managed
Additional Security Request (Strongly Recommended)

To further align with industry security standards, we also request:

Masking of all AI/API keys on the dashboard (e.g. sk-xxxx-xxxx)No plain-text display of API keys at any pointOptional “Reveal key” action with confirmation & permission control (or completely hidden if AI is system-managed)
Reference

We have demonstrated this behavior clearly in the attached video, where:

AI Training UI disappearsAI replies still work correctly in the background

This confirms that the requested feature is technically feasible within the current architecture.

I would request you to pls give the solution for this. There was already feature request raised for this which was in consideration from 5 months but no updates.