Review organization settings

On the Settings page, under Organization > Details (platform-ca | platform-eu | platform-au), you can review information and inputs relative to your organization:

To configure a Security Assertion Markup Language (SAML) single sign-on (SSO) for your Coveo organization, you must first configure your identity provider.

Then, enter the data you obtained during this first step on the Settings page, under Organization > Single sign-on (platform-ca | platform-eu | platform-au). This allows Coveo to work together with your desired identity provider. See Coveo SAML SSO for further details on the SSO configuration process.

On the Settings page, under Organization > Traffic (platform-ca | platform-eu | platform-au), you can review from which endpoint the traffic to your organization comes from.

In 2023, Coveo introduced organization endpoints, to which you can now send Coveo API requests. Although the generic platform endpoints (platform-<REGION>.cloud.coveo.com) will keep working, we now recommend you use the new search, analytics, and administration endpoints for a more seamless interaction with Coveo APIs. For details on this change, see Organization endpoints.

The Traffic subtab shows the endpoints used to call Coveo APIs and the traffic associated to each one. It also displays the endpoint Coveo recommends to use.

If your organization is deployed in multiple regions or if your license otherwise allows it, you can access the Regions subtab on the Settings page, under Organization > Regions (platform-ca | platform-eu | platform-au).

The Regions subtab displays the regions where your organization is deployed, along with their respective search traffic rates. The analytics traffic, on the other hand, is always sent to your primary main region.

Coveo automatically encrypts your data using its own encryption key to protect it from unauthorized access.

However, Coveo offers the alternative to encrypt your index data at rest with your own AWS KMS key. For details on this security enhancement, see Bring-your-own-key (BYOK) data encryption at Coveo.

The Encryption keys subtab allows you to manage the encryption keys that you bring to Coveo. For details on managing your encryption keys, see Manage your encryption keys.

On the Settings page, under Analytics > Internal events (platform-ca | platform-eu | platform-au), you can provide Coveo with your NAT or public IP addresses. Events associated with these addresses are then flagged as internal, that is, triggered by someone in your organization.

Enter a public IPv4 or IPv6 address or a range of addresses in the Classless Inter-Domain Routing (CIDR) notation, and then click Save.

Once you saved your internal addresses, you can create and apply a named filter on the Is Internal dimension (Is Internal Is not true) to remove your internal events from usage analytics reports.

You can also create and apply the Is Internal Is false filter to only report on external events.