LogoLogo
HomeDocumentationLog InSign Up
  • Welcome
  • Introduction
  • Getting Started
    • Overview
    • What can we do?
    • Features & Packages
    • SDKs
  • SERVICES
    • Introduction about services
    • Identity
      • Brand
        • Examples
        • How to identify a brand
        • What default values when a brand is created?
        • How to be a reseller
        • Multiple Brand Management
      • User *
        • User Type
        • Username
        • User Status
        • Username vs. Login Name
        • Password
          • User-defined options
          • Built-in policies
        • Authentication Methods
          • Traditional Login
          • External Login
          • Login with Email link
        • Referral (Invite Friends)
          • Example
        • Password Policy
        • Login with Google
        • Lock and Unlock Users
        • Suspend and Unsuspend Users
        • Delete Users
      • Device
        • Device Type
        • Device Identifier (Device Code)
        • Device Registering
        • Access Limit
    • Subscription
      • What is Package?
      • Package (Pricing Plan)
      • Plans & Pricing *
        • Licensing *
        • Subscription Type *
        • Feature
          • Examples
        • Package
        • Price *
        • Coupon
        • License
          • License Status
          • License Delivery Type
          • License Source
        • Pseudo Flow *
          • Licensing Flow *
          • Pricing Flow *
          • Coupon Application Flow *
    • Billing
      • Payment
        • Payment Status
        • Commission
        • Instant Payment Notification (IPN) *
          • Payment Gateway
          • Supported Gateways
        • Payment Transaction Overview
      • Transaction *
      • Invoice *
    • Wallet
      • Wallet *
        • Secure Practices *
        • ✔️Pseudo Flow *
      • Redeem *
    • Security
      • Black List
      • Risk Levels
      • Multi-Factor Authentication (MFA)
    • Community
      • Issue
        • Examples
        • Pseudo Flow
      • Organization
    • Content Delivery Network (CDN)
      • CDN
        • CDN Storage
        • Uploading files to a CDN
        • Downloading files from a CDN
        • Are There Any Limitations?
        • Best Practices
    • Analytics
      • Tracking
        • Tracking Activity
        • Tracking Email
        • Tracking Notification
      • Log & Debug
      • Notification
    • Integration
      • Authentication
      • Payment Gateways
      • Push Notification
      • SMS Provider
      • SMTP Provider
      • Gitbook
    • Brand Settings (Branding)
      • What are Permissions and Roles?
        • System permissions & brand-based permissions
          • A (6 resources)
          • B (7 resources)
          • C (4 resources)
          • D (3 resources)
          • E (2 resources)
          • F (1 resource)
          • I (3 resources)
          • L (1 resource)
          • O (1 organization)
          • P (4 resources)
          • R (1 resource)
          • S (2 resources)
          • T (4 resources)
          • U (7 resources)
          • W (1 resource)
        • System Roles & Brand-based Roles
        • Granting Permissions
        • Assigning Roles
        • Best Practices
        • Pseudo Flow
        • Conclusion
      • What is Issue Category
      • What is Feature?
      • What is Subscription Type?
      • What is Subscription?
      • What is Commission Rate?
      • Events & Patterns
        • Event
          • Events for Community (Organization) (4)
          • Events for Device (3)
          • Events for License (2)
          • Events for Payment (8)
          • Events for System (9)
          • Events for Ticket (Issue) (6)
          • Events for User (47)
            • User.Account_ (5)
            • User.Coupon_ (1)
            • User.Email_ (5)
            • User.Expiration_ (3)
            • User.Inactive_ (2)
            • User.Invoice_ (1)
            • User.License_ (1)
            • User.Logged_ (3)
            • User.Password_ (3)
            • User.Phone_ (2)
            • User.Profile_ (2)
            • User.Receipt_ (1)
            • User.Referee_ (1)
            • User.Registered (2)
            • User.Reward_ (3)
            • User.Service_ (1)
            • User.SMS_ (1)
            • User.Status_ (5)
            • User.Suspicious_ (4)
            • User.Ticket_ (1)
          • Events for Wallet (4)
          • (Missing Events) *
        • WalletEarningEvent
          • Earning.User_ (8)
          • Earning.Wallet_ (2)
        • Email Templates *
        • SMS Templates *
      • Tags
      • Domains
      • Email templates
      • Brand Link
    • System Constants (Read-only)
      • Country
      • State
      • City
      • Time Zone
      • Currency
      • Language
      • Exchange Rate
  • Other concepts
    • Built-in resource
      • Built-in roles
        • Best practice
      • Built-in permissions
    • JFW Status
    • Default data
    • System data
    • Soft deletion data
    • Cryptography
    • Mailing
      • Examples
      • Email Sender
      • Email Template
    • Scheduler
      • Examples
      • Schedulers Used In JFW
    • Tracking Level
  • Versioning
  • Workflows
  • References
    • Internal references
    • External references
      • MailKit
      • MIME Type
  • Changelog
Powered by GitBook
LogoLogo

For developers

  • Developers

For users

  • Admin & cPanel

Examples

  • BoostPTE

Copyright @2018-2025

On this page
  • Header
  • Body
  • Footer
  • Embedded Link

Was this helpful?

  1. SERVICES
  2. Brand Settings (Branding)

Brand Link

Create branded link with a custom logo, header, body, footer, links and more

Last updated 20 days ago

Was this helpful?

You can customize the appearance of your branding on cPanel and admin site, match the user interface to the language of your content, and more.

You can apply customizations to your entire references link as a site-wide theme, or to individual variants and site sections.

Each domain will have a different brand link layout configuration. This depends on the Header, Body, and Footer settings in the brand's admin site. Each domain can have an independent layout without causing confusion between brands.

Header

The Header section defines the topmost part of the page and plays a critical role in branding and navigation.

  • Header Logo:

Specifies the logo image URL for the current domain.

  • Header Search:

Enables a search bar in the header area.

  • Header Menu:

Defines the main navigation menu items. These links can point to internal pages or external resources.

  • Header Avatar:

Displays a user avatar or profile icon.

Body

The Body section is the main content area of the page.

  • Body Navigation:

Manages the side navigation (if applicable). Useful for dashboard-like layouts sites.

  • Body Header Slider:

A configurable slider or banner at the top of the body section, often used for promotions, announcements, or featured content.

  • Body Footer:

An optional area just above the actual site footer, used for secondary content such as quick links, newsletter subscriptions, or call-to-action banners.

Footer

The Footer section defines the bottom area of the page, typically containing legal, informational, and navigational links.

  • Footer Logo:

Allows inclusion of a brand logo in the footer for consistent branding.

  • Footer Description:

A short description or mission statement about the brand or website.

  • Footer Widget:

A customizable area within the footer that allows you to display structured content in multiple columns or blocks.

  • Footer Copyright:

Displays copyright information, often including the current year and brand name.

  • Footer Privacy Policy:

Link to the brand's privacy policy.

  • Footer Terms Of Use:

Link to the website’s terms and conditions or user agreement.

  • Footer Change Logs:

Link to the brand's change logs.

Embedded Link

To support flexible integration between the JFW system and client systems, we allow embedding logged-in user information into URLs through query parameters. This enables the client to handle and process the user data according to their own business logic.

Purpose

  • Allow client systems to easily identify and process users coming from the JFW platform.

  • Facilitate quick integration without the need for complex authentication mechanisms during early phases.

Parameter
Description

AuthKey

An identifier or session key (token) used for user authentication

ID

User ID in the JFW system

Username

The user’s login username

EmailAddress

The user’s email address

Security Considerations

  • The AuthKey should be encrypted or have a short expiration time to reduce security risks.

  • URLs containing user information should not be logged or shared publicly.

  • Client systems should validate and handle the data using their internal security standards.

Layout brand link design of Jframework system