Docs

AI Hub permissions

This article describes the permissions needed to use the AI Hub.

To set the permissions, you need to create a user role or edit an existing one and open the Permissions matrix. In the matrix, the permissions are collected into groups. Some of these groups can be expanded to set more granular permissions.

How to read this list

In this article, each heading describes an action. The permissions for that action are described in the form of breadcrumbs.

For example, if the required permissions are:

  • Profiles > Client list: read
  • Search engine: create, edit

The permission matrix needs to look like this:

Permission matrix in Synerise Settings showing Profiles with read access on Client list and Search engine with create and edit permissions
Permission example, see description above figure.

The read permission is not explicitly listed when any higher permission is required - the portal enables it automatically.

I want to...

work with AI Recommendations

NOTE: For permissions needed to configure the AI engine, see "Settings permissions".

see Recommendations and statistics

  • Communications > Recommendations: read
  • Assets > Catalogs: read

preview a Recommendation

  • Profiles: read - to search or select a profile from the list of all profiles
  • Analytics > Segmentations: read - to select a profile from a segmentation

see Recommendation details, create and edit a recommendation

  • Communications > Recommendations: create, edit
  • Settings > AI engine configuration: read
  • Analytics > Aggregates, Expressions: read
  • Search engine: read

This also enables saving and activating a Recommendation.

duplicate a Recommendation

Communications > Recommendations: create, edit

delete a Recommendation

Communications > Recommendations: delete

work with Recommendation A/B/X tests

  • Recommendation permissions as described above
  • Communications > Test optimizer:
    • read - to see the tests
    • create, edit - to create and edit tests
    • execute - to run tests

work with promotions

see promotions

  • Communications > Promotions: read
  • Analytics > Segmentations, Expressions, Aggregates: read

create, update and duplicate promotions

  • Communications > Promotions: create, edit
  • Assets > Tags: read
  • Assets > Catalogs: read

publish and hide promotions

Communications > Promotions: create, edit

delete promotions

Communications > Promotions: delete

import promotions

See "Import data" in "Data Management permissions".

work with personalized promotions

see personalized promotions

Communications > Personalized promotions: read

create, edit, and duplicate personalized promotions

  • Communications > Personalized promotions: create, edit
  • Assets > Catalogs: read

publish and unpublish personalized promotions

Communications > Personalized promotions: create, edit

delete personalized promotions

Communications > Personalized promotions: delete

This allows you to see the indexes and suggestion indexes.

NOTE: For permissions needed to configure the AI engine, see "Settings permissions".

  • Search engine: read
  • Settings > AI engine configuration: read
  • Assets > Catalogs: read
  • For A/B tests: Communications > Test optimizer: read

edit indexes, suggestion indexes, and A/B tests

This includes managing synonyms and query rules.

TIP: Indexes may have individual access level configurations.
To check your access level, hover over the padlock icon in the index's entry in the index list.

Example: checking your access level on a search index
Example: checking your access level on a search index

To change the access level of an index, see Change index access settings.

  • Search engine: edit
  • Settings > AI engine configuration: edit
  • For A/B tests: Communications > Test optimizer: edit To run an A/B test, you need Communications > Test optimizer: execute
  • For query rules: Analytics > Segmentations: read

create indexes, suggestion indexes, and A/B tests

This includes managing synonyms and query rules.

  • Search engine: create
  • Settings > AI engine configuration: create
  • For A/B tests: Communications > Test optimizer: create
    To run an A/B test, you need Communications > Test optimizer: execute
  • For query rules: Analytics > Segmentations: read

preview search/suggestion results

Profiles > Client list: read - to select a preview context profile

delete indexes, suggestion indexes, and A/B tests

This includes managing synonyms and query rules.

TIP: Indexes may have individual access level configurations.
To check your access level, hover over the padlock icon in the index's entry in the index list.

Example: checking your access level on a search index
Example: checking your access level on a search index

To change the access level of an index, see Change index access settings.

  • Search engine: delete
  • Settings > AI engine configuration: delete
  • For A/B tests: Communications > Test optimizer: delete

access Predictions

This allows you to see the predictions:

  • Predictions: read
  • Settings > Predictions: read
  • Settings > AI engine configuration: read
  • Search engine: read
  • Assets > Catalogs: read

create and edit predictions

  • Predictions: create, edit
  • Analytics > Expressions: read

calculate, deactivate, and duplicate predictions

Predictions: create, edit

clone a prediction to another workspace

In the source and target workspace, you need:

  • Cloning: create
  • all permissions for the cloned prediction and all nested objects that will also be cloned in the process.

To learn more about cloning, see Cloning objects to other workspaces.

use the System Agent with workspace resources

These permissions apply when the access level in the System Agent settings is Workspace resources. With the Documentation only access level, no permissions are required.

  • AI Agents > Platform Agent:
    • read - to let the agent browse and view resources for you
    • create, edit - to let the agent create and edit resources for you. This also requires Write in the allowed actions of the System Agent settings.
  • Permissions for the resources you want the agent to work with. For example, to let the agent preview segmentations, you need Analytics > Segmentations: read

By default, the Platform Agent permission is granted to the basic roles (PROFILE_ADMIN and PROFILE_MANAGER) and to the predefined Synerise roles. For custom roles, you must grant it yourself.

The agent never does more than your permissions allow.

use the Synerise MCP Server

These permissions apply when the access level in the Synerise MCP Server settings is Workspace resources.

  • AI Agents > MCP Server:
    • read - to let an external AI client browse and view resources for you
    • create, edit - to let an external AI client create and edit resources for you. This also requires Write in the allowed actions of the Synerise MCP Server settings.
  • Permissions for the resources you want the client to work with. For example, to let the client preview segmentations, you need Analytics > Segmentations: read

An external AI client never does more than your permissions allow.

Canonical URL: https://hub.synerise.com/docs/settings/identity-access-management/permissions/ai-hub-permissions