Branding

CloudBlue Connect allows Providers to brand (white-label) various aspects of its portals, as shown in the below example: 

Branding can only be configured by Connect staff and doesn’t currently have self-service configuration in the Provider Portal. This article covers various elements of the branding configuration and covers data that must be provided to your account manager to configure the branding.

Portals Branding

Different portals of Connect (Vendor Portal, Provider Portal and Customer Activation Screens) supports branding that includes the following attributes:

Email Notifications Branding

Connect sends in multiple cases emails to different actors, for example when a vendor receives a new request, connect may send him a notification. Provider may customize three (3) aspects for it’s brand:

User Agreement Branding

Connect may enforce the acceptance of a user agreement each time that a user is enrolled on any of it’s portals. This enrollment may happen due the creation of new vendors accounts, or due an existing vendor invites a new user to his account. The user will need to supply it’s contact data and agree with the agreement that may be referenced from an external source

Help Portal Branding

Providers have an option to either deploy branded help portal or redirect users to any external URL managed externally.

In case that external url is desired, Connect will send a JWT signed with agreed secret that will contain following information:

{
  "redirect": {
    "path": "/support/tickets/new", ## Agreed path where to redirect
    "brand": "vendor.XXXXXXX", # Brand 
    "system": "help" 
  },
  "user": {
    "id": "UR-841-574-187", # Unique ID of the individual user
    "accounts": [ # Array of accounts that such user may be able to access
      {
        "id": "PA-425-033", # id of the account
        "name": "ACME Provider" # Name of the vendor account
      },
      {
        "id": "VA-004-290", #Unique user id
        "name": "John Doe" #Name of the user
      }
    ],
    "emails": [
      john.doe@null.com # Array of emails of the user
    ],
    "name": "John Doe" #User first and last name
  },
  "exp": 1538746869 #Token Expiration
}

Support Portal Branding

Providers have an option to either deploy branded support portal experience (managed by Ingram Micro staff) or redirect users to any external URL of the ticketing system, managed externally. 

In case that external url is desired, Connect will send a JWT signed with agreed secret containing following information:

{
  "redirect": {
    "path": "/support/tickets/new", ## Agreed path where to redirect
    "brand": "vendor.XXXXXXX", # Brand 
    "system": "tickets" 
  },
  "user": {
    "id": "UR-841-574-187", # Unique ID of the individual user
    "accounts": [ # Array of accounts that such user may be able to access
      {
        "id": "PA-425-033", # id of the account
        "name": "ACME Provider" # Name of the vendor account
      },
      {
        "id": "VA-004-290", #Unique user id
        "name": "John Doe" #Name of the user
      }
    ],
    "emails": [
      john.doe@null.com # Array of emails of the user
    ],
    "name": "John Doe" #User first and last name
  },
  "exp": 1538746869 #Token Expiration
}

SSL Certificates

Connect users interacts with the platform using 4 different domains / access points, each of following access points are protected using an SSL certificate

• Provider portal
• Vendor portal
• Fulfillment API endpoint
• Activation screen for end customers

In order to issue you a CSR you will need to provide the following information:

Requesting your brand

In order to request a brand creation, please contact your Technical Account manager and provide following table filled changing the Example values for desired ones:

Translate with Google

English

Arabic Chinese (Simplified) Dutch English French German Italian Portuguese Russian Spanish