How to Hide the Login Option in the Customer Portal
Create a Public‑Only customer portal experience by removing the visible log‑in prompt. This guide shows how to hide the login button/tab on both desktop and mobile using Custom CSS, without changing backend authentication or user status.
Hiding login in the UI does not deactivate user accounts or block direct login URLs. Users who already have active sessions remain signed in until they log out or their sessions expire.
What This Change Does (and Doesn’t)
Does:
- Hide the Login button in desktop layouts.
- Hide the Login tab/button in mobile navigation.
Doesn’t:
- Deactivate accounts or sign out already authenticated users.
- Block access via a direct login URL (e.g.,
/login). - Affect the Agent Portal (
/agent) or email channel.
Steps to Hide Login via Custom CSS
1) Navigate to Customization
Go to Admin → Customer Portal → Customization → Custom CSS.
2) Paste the CSS
Use the following CSS to hide the login entry points:
.create-ticket-btn-web-view #login-button,
#mobile_login_tab
{
display: none !important;
}
To know where to paste the above custom CSS code, explore more on BoldDesk Customer Portal Customization: Step-By-Step Guide.
Before Customization
After Customization
- Portal sign‑in cannot be restricted for users with active accounts; access must be revoked by deactivating users’ accounts.
- The customization to hide the Login feature using Custom CSS applies to all customer portal visitors.
Frequently Asked Questions (FAQ)
Q1: What does the “Hide Login via CSS” change do in the BoldDesk Customer Portal?
A: It removes the visible Login controls from the portal UI by hiding the desktop login button and the mobile login tab using Custom CSS. This is a cosmetic change to the portal interface; it does not alter authentication settings or user accounts.
Q2: Which exact elements are hidden by the CSS snippet?
A: The rules .create-ticket-btn-web-view #login-button and #mobile_login_tab hide the Login button in desktop layouts and the Login tab/button in mobile navigation, respectively.
Q3: Does hiding the login button sign users out or deactivate their accounts?
A: No. Hiding the Log in button with CSS does not sign out users, end sessions, or deactivate accounts. Users who are already signed in remain authenticated until they log out or their sessions expire.
Q4: Can users still reach the login page directly (e.g., /login) or via SSO redirect?
A: Yes. CSS only affects visual elements; it does not block routes or authentication flows. A direct link to the login page (such as /login) or an SSO‑initiated redirect will still function.
Q5: Who is affected when the login button is hidden?
A: All visitors to the Customer Portal (Agents, Contacts, and Visitors) see the login UI removed because CSS applies globally to the portal’s front end.
