Microsite Framework

Key Benefits

• Upload your static files (HTML, CSS, JS, images, etc.) to your assigned FTP folder
• Your site will be instantly available at its own subdomain
• No complex deployment pipelines or CI/CD setup required
• Perfect for microsites, landing pages, and campaign websites

products.json Structure

The products.json file supports flexible access control through three different configurations:

1. Product-Based Access Only

Restrict access to users who have access to specific products:

{
  "products": [
    {
      "serviceArea": "WMC",
      "productCode": "US"
    },
    {
      "serviceArea": "Global",
      "productCode": "EU"
    }
  ]
}

2. Role-Based Access Only

Restrict access to users with specific roles (e.g., staff-only sites):

{
  "roles": [
    "Staff"
  ]
}

3. Combined Product AND Role Access

Require users to have BOTH a specific product access AND a specific role:

{
  "products": [
    {
      "serviceArea": "GCS",
      "productCode": "GLO_CON_SER_EN_DB"
    }
  ],
  "roles": [
    "Shebboleet"
  ]
}

4. Simple Password Protection

Protect a microsite with a shared password. Visitors will be prompted to enter the password before accessing any content. No SSO or user account required:

{
  "password": "my-secret-password"
}

Properties:

• products (optional) - Array of product access requirements
  • serviceArea - Defines the service area or department (e.g., "WMC", "Global", "GCS")
  • productCode - Specifies the product or region code (e.g., "US", "EU", "GLO_CON_SER_EN_DB")
• roles (optional) - Array of role names that grant access (e.g., "Staff", "Admin", "Shebboleet")
• password (optional) - A fixed password string for simple password-based access control

How It Works

The presence of products.json enables automatic authentication integration with flexible access control logic:

Access Logic:

• Password: When a password field is present, visitors are shown a simple login form. After entering the correct password, access is granted for 24 hours via a secure cookie. SSO authentication is bypassed entirely.
• Products only: Users who have access to any product listed will gain access to the microsite
• Roles only: Users who have any role listed will gain access to the microsite
• Both products and roles: Users must satisfy both requirements - they need access to at least one listed product AND have at least one listed role

Use Cases:

• Public microsites - Omit products.json entirely for unrestricted access
• Product subscribers - Use products array to restrict by service area and product code
• Staff-only sites - Use roles array to create internal-only microsites
• Premium features - Combine both to require specific product access plus a special role
• Shared password sites - Use the password field for simple access control without requiring user accounts (e.g., event pages, previews, or external collaborators)

Note: This is an all-or-nothing access model - there is no page-level or content-level restrictions within the microsite.