Configuration of Composum AI in AEM

OpenAI API Key and general configuration

The Composum AI can be configured to use OpenAI services or other LLM that have a compatible interface, like local LLM.

{
  "jcr:primaryType": "nt:unstructured",
  "openAiApiKey": "sk-******"
}

Composum AI Prompt Library Configuration

Composum AI provides a default prompt library for the Content Creation Assistant and the Side Panel Assistant. It is quite likely that you will want to customize the prompts or add new prompts for your specific use case, or use prompts in a different language than english. This can be done with the “Composum AI Prompt Library Configuration”. There is an OSGI configuration that can set system-wide default paths, and a Sling Context Aware Configuration that can override these defaults for specific parts of the site.

These paths can be paths to a JSON file like predefinedprompts.json . To make it easy to maintain a prompt library, it is also possible to use content pages as prompt library. The content page should have a simple structure and the prompts should be as components in exactly one container containing components with the prompts. Usable for the prompt components are e.g. teasers or other components that have:

1. a title property (jcr:title, title or subtitle) that is taken as title of the prompt, and
2. a text property (jcr:description, description or text) that is taken as the text of the prompt.

If you want to adapt the default prompt libraries

/conf/composum-ai/settings/dialogs/contentcreation/predefinedprompts

/conf/composum-ai/settings/dialogs/sidepanel-ai/predefinedprompts

these can be copied into the site or some other place and edited there. They do, however, use components and page template of the WKND site, so you might need to change the components and page templates to match your site.

If the paths to the prompt libraries contain language specific subpages (en, de and so forth), the prompt library in the language of the site is taken, falling back to en.

AI Permission Configuration

For the permission configuration we use sets of configuration entries that each allow the use of some of the AI services (dialogs) in some context, and are additional - the corresponding AI dialogs are accessible if there is one configuration to allow it. There is however a fallback hierarchy for the permission configuration, where the fallback is only done if there is not a single visible entry in the fallback level:

• Sling Context Aware Configuration
• an OSGI configuration factory at “Composum AI Permission Configuration”
• a single OSGI configuration at “Composum AI Permission Configuration” that is the default configuration when nothing else is found, and normally allows all services for all users etc. if not changed.

Thus, if the context aware configuration is not used and the factory is not used either, then the default “all allowing” configuration is used, which it is ignored otherwise. If using context aware configuration it's sensible to provide a default configuration at e.g. /conf/global/sling:configs/com.composum.ai.backend.slingbase.model.GPTPermissionConfiguration/entry1 that forbids everything for sites where sling context aware configuration is not configured as a default and thus deactivates the other fallback levels (OSGI) generally, and then add configurations for the parts where it is allowed.

For the sling context aware configuration, we have a configuration list at com.composum.ai.backend.slingbase.model.GPTPermissionConfiguration , which is also used in the OSGI configuration. It has the following properties:

The general principle is that a configuration allows using one or more services (that is, assistant dialogs) for everything that matches the allows* properties and does not match the denied* properties - thus the denied takes precedence.

It is possible to create several list entries allowing a subset of the services (dialogs) for a subset of users, sites, components and so forth. Permissions are additive.

Example: for allowing all services for all users etc. on the subtree /content/wknd you could have the following entry at /conf/wknd/sling:configs/com.composum.ai.backend.slingbase.model.GPTPermissionConfiguration/entry1 if /content/wknd/jcr:content has a sling:configRef pointing to /conf/wknd.

{
  "jcr:primaryType": "nt:unstructured",
  "services": [
    "categorize",
    "create",
    "sidepanel",
    "translate"
  ],
  "allowedUsers": [
    ".*"
  ],
  "deniedUsers": [
    ".*"
  ],
  "allowedPaths": [
    "/content/.*"
  ],
  "deniedPaths": [
    "/content/dam/.*"
  ],
  "allowedViews": [
    ".*"
  ],
  "deniedViews": [
    ""
  ],
  "allowedComponents": [
    ".*"
  ],
  "deniedComponents": [
    ""
  ],
  "allowedPageTemplates": [
    ".*"
  ],
  "deniedPageTemplates": [
    ""
  ]
}

Specification

For even more details see the specification