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.
Different portals of Connect (Vendor Portal, Provider Portal and Customer Activation Screens) supports branding that includes the following attributes:
# | Attribute | Description |
1 | Favicon | Image shown on the browser |
2 | Logo | Logo of the provider, to be shown in Provider and Vendor Portals |
3 | Main color | Main color used on the different screens, including the top frame on top after accessing the portals |
4 | Name | Name of the different portals, we may specify different name for provider and vendor portals |
5 | Domains | Domain where the different portals must answer, for example: Provider Portal: https://provider.example.com Vendor Portal: https://vendor.example.com Activation UI for customers: https://activate.example.com API endpoint: https://api.example.com |
6 | Title | Title to be shown on the Vendor or Provider portal, each one may have different title |
7 | Sign UP URL | In case that provider runs a program to allow onboarding of vendors, url where to redirect them in case that vendor has no account |
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:
# | Attribute | Description |
8 | Company | Company name used as sender of email notifications |
9 | Address | email address uses as from value for emails |
10 | Footer | Text that will be added at the bottom of each email sent by connect platform, it may contain the standard disclaimer of emails sent by the company |
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
# | Attribute | Description |
11 | User Agreement | URL where to redirect customers to read the user agreement |
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
}
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
}
Connect users interacts with the platform using 4 different domains / access points, each of following access points are protected using an SSL certificate
In order to issue you a CSR you will need to provide the following information:
# | Attribute | Example |
16 | Organization | Acme Inc |
17 | Organizational Unit | Acme Cloud |
18 | Country | US |
19 | State | California |
20 | Locality | Irvine |
21 | Email Address | John.doe@acme.com |
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:
# | Attribute | Example |
1 | Favicon | https://vendor.connect.cloud.im/favicons/vendor/favicon.ico |
2 | Logo | https://vendor.connect.cloud.im/logos/logo.svg |
3 | Main color | Rgb(136,0,7) |
4 | Name | – Provider Portal: provider.connect.domain.com – Vendor Portal: vendor.connect.domain.com – Activate UI: activate.connect.domain.com – Fulfillment API: api.connect.domain.com |
5 | Domains | – Provider Portal: provider.connect.domain.com – Vendor Portal: vendor.connect.domain.com – Activate UI: activate.connect.domain.com – Fulfillment API: api.connect.domain.com |
6 | Title | – Provider Portal: “ACME PROVIDER PORTAL” – Vendor Portal: “ACME VENDOR PORTAL” |
7 | Sign UP URL | https://vendorprogram.domain.com |
8 | Company | Acme Inc |
9 | Email Address | no-replay@acme.com |
10 | Footer | This email may contain material that is confidential, and proprietary to Acme Inc, for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.” |
11 | User Agreement | https://www.acme.com/eulas/user_agreement_vendors.html |
12 | Help URL | https://kb.acme.com |
13 | Help Secret | 7vpdcAdtP |
14 | Support URL | https://support.acme.com |
15 | Support Secret | ZqdiMgB8h |
16 | Organization for CSR | Acme Inc |
17 | Organizational Unit for CSR | Acme Cloud |
18 | Country for CSR | US |
19 | State for CSR | California |
20 | Locality for CSR | Irvine |
21 | Email Address for CSR | john.doe@acme.com |