This section guides the Administrator on how to set global options for the visibility or enablement of certain features of the Platform.

These settings must be applied separately for the different Stakeholder Types. The settings will only be explained once for Internal stakeholders, as the settings for the other stakeholders are always a subset of those. The Stakeholder Types can be summarized thusly:

• Internal: Users who belong to internal Organizations. They are involved in the end-to-end governance of the entities of the Platform (digital products, Apps…).

• External: Users who belong to Partner or Citizen Organizations. In other words, external users who have been onboarded onto the Platform, generally to consume digital products or consult the catalogs.

• Guest: Users who have registered on the Platform but have not been onboarded on any Organization.

• Visitors: Users who have not logged into the Platform. NOTE: This applies only if the Public Showcase is enabled for your installation.

The settings in this section are useful in case you want the types of stakeholders defined above to only see limited sections, features or information, or if you want to disable certain features altogether.

NOTE: Some areas may be shown as unavailable, because the corresponding feature is not enabled for your installation. Ask your Customer Success representative for more information.

NOTE2: This section was previously called Features.

Managing Profiling and Features Settings

The following actions apply similarly for each of the settings described in the sub-chapters below. Each area has an enabling switch and a set of options: switches that show or hide a feature in a part of the Platform, and lists from which you select the available values (for example the searchbar filters and the table columns).

Editing profiling and features settings

Steps:

1. Navigate to Administration > Access Management > Profiling.

2. Select the stakeholder type in the navbar (Internal, External, Guest, Visitor).

3. Search for the related feature or setting and expand its section.

4. Use the section toggle to enable or disable the feature, and edit its settings as described in the dedicated chapter.

5. Click Save.

NOTE: When a section is disabled, its settings remain visible but read-only until it is enabled again. Some fields appear or disappear depending on the values you choose; if a value is not valid, it is flagged and the settings cannot be saved until it is corrected.

Restoring profiling and features settings

You may restore the default settings defined at the initial tenant setup for each specific setting or for all settings at once.

NOTE: If you want to update your default settings to your current settings, contact support.

Steps:

1. Navigate to Administration > Access Management > Profiling.

2. Select the desired stakeholder type in the navbar to whom your actions should apply.

3. Click Restore default settings.

4. In the prompted window select any or all of the settings you want to restore (Select all entities). You may see what the default was before selecting it.

5. Click Restore selected entities.

Exporting and importing profiling and features settings

For each stakeholder Type, you may want to save, store, and restore a particular mix of the settings in this section, or copy it between environments. The storing format is a structured JSON.

Steps:

1. Navigate to Administration > Access Management > Profiling.

2. Select the desired stakeholder type in the navbar to whom your actions should apply.

3. Click Export settings to download the settings.

4. Click Import settings to load the settings. The settings are not yet applied.

5. Click Save.

NOTE: A file exported for a stakeholder type cannot be imported for a different one.

Searchbar filters and table columns

Most areas let you configure the available searchbar filters (for the Catalog and for the Workspace) and the columns visible in table view. Hiding filters is important if you want to hide the information related to those filters.

For example if you don't want users exploring the Catalog to see who the Owners are, you should deselect the "Owner" filter and the related column.

Profiling & Features – Digital Products

NOTE: Digital products other than APIs are available only if enabled for your installation.

Here you may enable or disable Digital Products entirely. If enabled you may choose whether or not:

• To show the Digital Products section in the Workspace.

• To show the Digital Products section in the Catalog.

• Which searchbar filters and table columns are available in the Workspace and Catalog.

Profiling & Features – Active Catalog

Here you may choose between the two types of catalog:

• API Catalog: only APIs (products) and assets;

• Active Catalog: a single catalog for all digital products (APIs, MCP servers, AI Agents and the other types enabled for your installation), with filters by type, card and table views, saved filters and column management.

If Enable Active Catalog is selected, the users of that stakeholder type see the Active Catalog instead of the API Catalog (never both).

Profiling & Features – APIs (Products)

Here you may enable or disable API Products entirely. If enabled you may choose whether or not:

• To show the API Products section in the Workspace.

• To show the API Products section in the Catalog. In this case you may also choose to show a:

  • Minimal Identity Card: if selected you may choose to display users a reduced version of the Identity Card of the API. The only fields that remain visible are: Categories, Last Update and Status.

  • NOTE: To make sure information is properly hidden, use this setting in conjunction with the searchbar filters and table columns.

• To show the Desynchronization API Warnings: warnings for APIs whose specification is not aligned with the API gateway.

Profiling & Features – Assets

NOTE: API Assets are available only if enabled for your installation.

Here you may enable or disable API Assets entirely if and only if the API Products feature is enabled.

This affects the Workspace, the API forms, and all labels that consider the difference between Product and API. If enabled you may choose whether or not:

• To show the Assets in the Workspace.

• To show the Assets in the Catalog.

NOTE: The Assets feature is generally intended for internal stakeholders. By default it will be disabled for all other stakeholders.

Profiling & Features – Applications

Here you may enable or disable Applications entirely. If enabled you may choose whether or not:

• To show the Applications in the Workspace.

• To show the Applications in the Catalog.

NOTE: The Applications feature is fundamental for subscribing to APIs. It is generally recommended to have it enabled at least for internal users.

Profiling & Features – Keys

Here you may enable or disable the feature of Keyset Management. The feature is not mandatory, but disabling it will prevent you from managing Keyset Policies for your API subscriptions (see chapter Security governance).

NOTE: The feature may be enabled or disabled at any time without impacts on the Subscriptions (Keys are still managed under the hood, and retrieving credentials always remains available).

NOTE2: The feature makes sense when paired with an integration to a Key Provider (like an API gateway or an identity provider).

Profiling & Features – Subscriptions

Here you can choose whether to limit or display certain information and options in the API Product Subscription window in the Catalog and the Subscription Inspection window in the Workspace:

• Show IP Field: if enabled, subscribers will be able to declare which IP or set of IPs their Application will be calling the API from (the IP step of the subscription wizard, also editable on active subscriptions). This is useful if a whitelist is in place on the API provider's side. Each new IP is reviewed separately by the users with the related permissions (see chapter Organizations and users, Permissions). This setting is disabled by default.

• Minimal Card: hides fields in the Subscription. This affects the related entity cards; the fields that remain visible are: name, status and version.

  • NOTE: To make sure information is properly hidden, use this setting in conjunction with the searchbar filters and table columns.

Profiling & Features – Network

This setting lets you enable or disable the Network section of the Workspace, where the client IP addresses declared in subscriptions and the lists they belong to (for example allowlists) are managed. When disabled, the IP address and list pages are no longer accessible.

You can also choose the searchbar filters and the columns of the IP address and list tables.

NOTE: It is recommended to enable the Network section only for the stakeholders who are in charge of reviewing IP addresses, generally internal users.

Profiling & Features – Documentation

This section lets the Administrator enable or disable the Documentation feature altogether. If enabled you may choose to:

• Show in Workspace: when selected the Documentation feature will be available for digital products in the Workspace, making their documentation editable.

• Show in Catalog: when selected the Documentation feature will be available in the Catalog for digital products. Select this if you want to display their documentation to users exploring the Catalog. Documentation visibility settings still apply for each digital product (see chapter Default entity visibility).

• Show in Global Section: enables Global documentation (unrelated to digital products), in the Documentation section of the sidebar. Documentation visibility settings still apply.

• Allow Creation: allows the creation of new Documents in the Global section for any users with related permissions. Disable this if you don't want any users to create Global documentation.

• Minimal Card: limits the Documentation card to a minimal version. If enabled, only the essential fields are shown in the Documentation card. Use this to hide internal information from global documents.

Profiling & Features – Organizations

This setting lets you enable or disable the Org Admins Group from showing up in any organization. Disable this if you are not interested in that default group or you want to hide that group from certain stakeholder types.

NOTE: Disabling this feature for external stakeholders may be recommended if their onboarding is strictly handled by internal users.

Profiling & Features – Invitations

This setting lets you enable or disable the invitations feature. Enable this feature if you want to be able to onboard users by inviting them via their email, and you want to be able to manage the invitations with the dedicated Invitations section.

Profiling & Features – Join Requests

This setting lets you enable or disable the Join Requests feature. Enable this feature if you want to let users request to join your organizations, and you want to be able to manage the requests with the dedicated Join Requests section.

NOTE: It's important to disable this feature for external stakeholders and guests if you don't want them to be able to view which your tenant's Organizations are.

Profiling & Features – API Analytics [CUSTOM SETTING!]

This setting lets you enable or disable the Analytics section. The Analytics section is a custom section and it works only under certain conditions: it requires an additional configuration of your installation. Ask your Customer Success representative if this feature applies to your infrastructure.

If enabled, you may choose to show the analytics section:

• In the Workspace: displays the Analytics tab for each API in the workspace. Analytics are filtered for that API.

• In the Catalog: displays the Analytics tab for each API in the Catalog. Analytics are filtered for that API.

• Globally: displays the Analytics section in the sidebar. This provides an unfiltered view of the analytics, which can be further filtered later.

Profiling & Features – API Designer

This setting lets you enable or disable the API Designer, the editor of the OpenAPI definitions of REST APIs. If enabled you may choose:

• In Global Section: this displays the Designer in the sidebar.

Profiling & Features – AI Chat

NOTE: AI assistants are available only if enabled for your installation.

This setting lets you enable or disable the AI assistants. If enabled you may choose:

• AI Chat in API Designer: this enables the AI assistant in the API Designer (the Ask AI button), which helps users write and improve OpenAPI definitions.

Profiling & Features – History

This setting lets you enable or disable the History Tab in each digital product and App. If enabled you may choose to show the tab:

• In Catalog: this will display the History Tab in the Catalog.

• In Workspace: this will display the History Tab in the Workspace.

NOTE: It is recommended to have it always enabled in the Workspace. You may want to consider disabling it in the catalog for external Stakeholders and Guests, if you don't want to show the lifecycle of your digital products externally.

Profiling & Features – Domains and Environments

These settings let you manage certain settings regarding how domains and environments are displayed in the Platform. Specifically you may choose to:

• Show Private Domains: enabling this will display back-end domains or IPs where APIs are exposed internally.

  • NOTE: It is recommended to have this setting enabled only for internal stakeholders.

• Change the Environments Display Order: you can choose ascending or descending. If no preference is provided, sorting will be descending.

• Manage the visibility and labelling of environments: this setting lets you choose, for each type of organization, if an environment will be visible (Logic Name), and if so, if it should be displayed by a different name (Display Name). This is useful if, for example, you want external users to know your "QA" environment by the name "TEST".

  • NOTE: Custom labels are not translated.

Profiling & Features – Use Cases

This setting lets you enable the Use Cases feature. If enabled for certain stakeholders, those stakeholders will be able to optionally add Use Cases when creating a Subscription, and manage those Use Cases in the dedicated section under their Applications.

NOTE: You may enable or disable this feature anytime, as it has no impact on the lifecycles of the core entities of the Platform.

Profiling & Features – Account (User ID)

This setting lets users see the external ID of other federated users (in case of SSO) alongside their email in the different places where users are displayed.

This is useful when federated users, such as technical user accounts, might be sharing the same email address, and another way to distinguish users is required.

NOTE: You may enable or disable this feature anytime, as it has no impact on the lifecycles of the core entities of the Platform.

Profiling & Features – KPI Visibility in the Web Application

Certain pages display tenant-wide KPIs regarding core entities and users. You may wish to hide this information for certain user types.

It is possible to configure the visibility of certain core KPIs in the Homepage, Users and Organizations sections, and in the Catalog.

Steps:

1. Navigate to Administration > Access Management > Profiling.

2. Choose the Stakeholder Type you want the setting to apply to (Internal, External, Guest, Visitor).

3. Search and select the KPI settings card.

4. Enable or disable the KPI visibility.

5. Click Save.