Configuration
The <nu-evolution-editor> can be configured via attributes or properties to enable or disable features like profile catalogs or the save button.
Editor Capabilities
Capabilities are passed as a space-separated string via the capabilities attribute, or as an array of Capability enums via the capabilities property.
<nu-evolution-editor token="your-access-token" capabilities="profile-catalog-open save-profile"></nu-evolution-editor>import { type NuEvolutionEditor, Capability } from '@nuitdev/evo-embedded'
const editor = document.querySelector<NuEvolutionEditor>('nu-evolution-editor')
if (editor) {
editor.capabilities = [Capability.PROFILE_CATALOG_OPEN, Capability.SAVE_PROFILE]
}Available Capabilities
| Capability | Value | Description |
|---|---|---|
PROFILE_CATALOG_OPEN | 'profile-catalog-open' | Enables the profile catalog to open saved profiles. |
PROFILE_CATALOG_SAVE | 'profile-catalog-save' | Enables the profile catalog to save profiles. |
SAVE_PROFILE | 'save-profile' | Adds a save button to the editor toolbar. |
ID & Identity Configuration
The editor uses several attributes to manage profile identification and upsert behavior.
| Attribute | Property | Description |
|---|---|---|
profile-id | profileId | The ID used to load a profile. Triggers an update on save. |
id-type | idType | Either 'default' (nuIT ID) or 'external' (your custom ID). |
Loading Examples
Environment
The env attribute selects which EVO backend the embedded iframe loads from. Allowed values are prod (default), staging, and dev.
<nu-evolution-editor token="your-access-token" env="staging"></nu-evolution-editor>The attribute is read once when the iframe is created and is not observed — changing it at runtime has no effect on an already-rendered editor. Omit it (or set prod) for production use.
Debug Mode
Adding the debug attribute will enable detailed logging in the browser's developer console.
<nu-evolution-editor debug></nu-evolution-editor>