Coveo Cloud V1 and V2 Compared
Coveo currently hosts organizations in two independent cloud platforms, the new Coveo Cloud V2 and Coveo Cloud V1, the original Coveo offering in the cloud. The table below outlines the main differences between the two Coveo Cloud versions as well as the Coveo cloud services that they share.
Contact your Coveo Customer Success Manager (CSM) or your sales representative to schedule a meeting with professional services to proceed, when possible, to the migration of your Coveo Cloud V1 organization to Coveo Cloud V2.
|Platform||Coveo Cloud V2||Coveo Cloud V1|
|Architecture||Fully scalable native cloud service||On-premises solution adapted and ported to the cloud|
|Development||Regular releases with new features||Maintenance with limited new features|
|Organization hosting||New customers||Progressive migration of existing customers to Coveo Cloud V2|
|Coveo Cloud shared services|
Note 1: Since the November 30th, 2017 release, all new usage analytics features are only made available in Coveo Cloud V2.
Determining in Which Coveo Cloud Version Your Organization Is Hosted
An organization member who has access to the Administration Console can identify on which Coveo Platform version his organization is hosted by the Administration Console look and URL (see the table above).
End users can’t tell from which Coveo Platform version they get their search results.
Other Differences with Coveo Cloud V2
Coveo Cloud V1 doesn’t manage users and passwords as Coveo Cloud V2 does. All Coveo Cloud V2 organization members must be users of one of the supported identity providers, which are Salesforce, Office 365, and Google (enterprise and personal such as Gmail) [see Logging in to Coveo Cloud V2]. Single sign-on is also supported in Coveo Cloud V2 (see Coveo Cloud V2 SAML SSO). However, since Coveo Cloud V2 doesn’t manage the authentication process, you can’t create custom users.
You must provide the emails of all users you want to add in the organization. In Coveo Cloud V2, you can add all users from a provider in a single step (see Adding and Managing Groups).
You assign role(s) to your organization users (see Coveo Cloud V1 Organization User Roles). Each role provided the user predetermined set of permissions that aren’t customizable. In Coveo Cloud V2, groups and privileges replace roles, and since privileges are granular, administrators can grant or deny organization group member access to each feature and service (see Privilege Management and Adding and Managing Groups).
The concept of organization owner no longer exists in Coveo Cloud V2. Instead, the organization contact (by default the first member of the organization) receives important emails from Coveo Support (see Organization ID and Other Information).
The trial of an organization in Coveo Cloud V2 lasts 30 days and gives access to all available connectors.
License update in Salesforce are synchronized in Coveo Cloud V2.
You need to contact Coveo Support to create API keys. In Coveo Cloud V2, API keys can be created by a member of a group that has been granted the Can Create ability for the API Keys domain (see Privilege Management).
Sources are no longer editable using the Administration Console once the source JSON configuration has been modified. In Coveo Cloud V2, source configurations are always editable using the Edit a Source JSON Configuration panel and the Edit a <SOURCE_TYPE> panel, meaning that source configurations can’t be locked (grayed) in the Administration Console.
You must rebuild a source after changing its configuration, even if your changes don’t affect the indexed items. In Coveo Cloud V2, you can apply source configuration changes such as source credentials updates using a source refresh or rescan. Rebuilds are only required when changes must be applied to all source items.
There are more connectors available in Coveo Cloud V2.
The metadata and extraction method are all set during the field creation process. In Coveo Cloud V2, you choose the metadata to be used as the field source and the metadata extraction method when you add mappings for a particular source (see Add or Edit a Mapping Rule).
You must create the same field for each source in which you expect to use it. In Coveo Cloud V2, a field can be used by several sources (see Reference).
Fields in Coveo Cloud V2 don’t have aliases, and fields with a
sysprefix only exist for compatibility reasons (see About the SYS Field Name Prefix).