Overview
Parameters:LOGO_LINK_URL
Category: Custom
Default value: Empty (no link)
Product: eTASK.Other (Custom)
What does this parameter do?
This parameter determines the destination URL linked to the company logo in the upper-right corner of the eTASK portal. When you click on the logo, you are redirected to the specified web address. If the parameter is empty, the logo remains unlinked and serves only for visual display.
What is this parameter used for?
Link to the company website: The logo in the portal links directly to your company’s homepage
Link to the intranet homepage: Employees can access the internal company platform by clicking on the logo
Navigation to support portals: Direct access to help or service pages via the logo
Branding and brand identity: Strengthening corporate identity through linked company representation
User-friendliness: Intuitive navigation through the familiar "click-on-logo" convention
Technical Details (for Administrators)
Format: Full URL (string)
Default value: Empty (no link)
Valid values:
Full URL:
https://www.beispiel-unternehmen.deIntranet URLs:
http://intranet.firma.localSubpages:
https://www.beispiel.de/supportEmpty: No link (logo not clickable)
Important notes:
The logo is used both on the login page and in the portal header after logging in
The URL must contain the full protocol (http:// or https://)
If the value is empty, the logo remains visible but is not clickable
By default, the link opens in the same browser window
The logo itself is uploaded via separate portal graphics settings
Interaction with other parameters:
HEADER_ALIGN: Determines the position of the logo (left or right in the header)
LOGIN_LINK_URL: Defines a separate link for the center section of the login form
When should you change this value?
Set the URL (link the logo) if:
You want users to be taken to the company website by clicking on the logo
The portal is embedded in a larger intranet and should redirect to the homepage
You want to enable direct access to support or help pages via the logo
Corporate identity guidelines require a linked logo
Users frequently switch between the portal and another company platform
Leave the value blank (do not link the logo) if:
The logo is purely decorative and is not intended to provide navigation
You want to prevent users from accidentally leaving the portal
There is no relevant landing page for a logo link
Users work exclusively within the portal and external links should be avoided
Security policies restrict external links
Important Notes
Full URL required Always
use the full URL, including the protocol (http:// or https://). Relative paths do not work correctly. Example:https://www.unternehmen.deinstead of justwww.unternehmen.de.Configure logo
graphic separately This parameter defines only the link, not the logo image itself. Upload the logo image via the portal graphics management (Control Panel > Portal Options > Portal Management > Portal Graphics).Link opens in the same window
By default, the linked page opens in the same browser tab. This causes users to leave the portal. Ensure this is the intended behavior, or inform users accordingly.Applies to login page and portal
The link works both on the login page and in the header of the logged-in portal. Both logos link to the same URL.Test the URL After configuration
, verify that the linked page is accessible and that there are no access restrictions (e.g., mandatory VPN) that could cause issues for users.
Security
Does changing this parameter affect security?
Yes, but the impact is minimal and primarily organizational in nature.
Note:
Phishing risk due to misconfiguration: Incorrect URLs could redirect users to unintended pages
External links: Links to external websites should only point to trusted sources
URL validation: Carefully check the destination URL for typos to avoid misunderstandings
HTTPS recommended: Use encrypted connections (https://) for enhanced security
Recommendation: Use only URLs that lead to your company’s official, trusted websites. Avoid external links to third-party providers. Test the URL before publication and inform users that clicking the logo will take them away from the portal if this is not obvious.
Practical example
Initial situation: A facility management company uses eTASK as part of its IT landscape. The company has a central intranet portal at https://intranet.fm-gmbh.de, where employees have access to all company applications, news, and resources. Currently, the eTASK logo is not linked within the portal, and employees must open a separate browser tab to return to the intranet.
Configuration: The administrator sets LOGO_LINK_URL to https://intranet.fm-gmbh.de and saves the change in the system configuration.
After the change:
Users can return directly to the intranet by clicking the company logo in the top-right corner of the portal
Navigation between company applications is simplified and more intuitive
The logo gains an additional function beyond its purely visual representation
Both on the login page and while logged in, the logo links to the intranet
Users perceive the integration as more seamless and professional
Result: User-friendliness increases significantly, as employees can intuitively navigate back to the central platform by clicking on the familiar company logo. The number of open browser tabs is reduced, and workflows become more efficient. The eTASK portal integrates better into the overall architecture of the IT landscape.
Recommended setting
For standard installations: Blank (No link)
Reason:
Prevents users from unintentionally leaving the portal due to accidental clicks
Reduces confusion among users who do not expect the logo to be clickable
No additional configuration required
Logo primarily serves a visual branding function
Exceptions (linking recommended):
Integration into a larger intranet landscape with a central portal
Frequent switching between different corporate applications
Corporate identity guidelines require linked logo display
Users expect logos to be clickable by default
Direct access to support or help resources is desired
Tip: When you enter a URL, choose a landing page that is relevant and accessible to all portal users. Avoid URLs that are only accessible to specific user groups (e.g., VPN-protected pages) to prevent frustration. Test the configuration with different user groups before putting it into production.