Requestable features

Requestable features are features that are not enabled by default on Verify tenants. As new features are delivered, requestable features allow customers, partners, and other users of Verify to provide feedback and experience early use. Requestable features are generally available and production ready features.

To enable requestable features on your tenant, open a support ticket and reference the requestable feature reference number, either starting with a “CI” or “VDEV”. If you are unable to open a support ticket, contact your IBM representative with the feature reference number.
Ask watsonx (VDEV-52267: Verify Analytics GenAI and VDEV-60440: Access policies)
  • Use a chatbot experience that is powered by watsonx to summarize large-scale identity attacks and generate access policies. You must first enable VDEV-52267 before proceeding with VDEV-60440.
  • For more information, see Gen AI assistant.
Content Security Policy (CSP) Header (VDEV-41592)
  • Mitigate your browser's vulnerability to XSS attacks. A CSP restricts how the browser interacts with endpoints. It can specify which domains a browser uses as trusted sources and the protocols that are used for data transfer.
  • For more information, see Configuring your endpoint settings.
Digital credentials (CI-46637)
  • Digital credentials allow organizations to issue and verify standards-based credentials by using a Digital wallet experience. Physical identity constructs can be digitized and used in online and in-person interactions.
  • For more information, see Managing verifiable credentials
Download reports as CSV files (CI-40542)
  • Reports in Verify now allow administrators to export and download the report data into a CSV file for post processing and other business processing needs. This feature is a prerequisite for User list report (CI-74090).
  • For more information, see Download a .csv report.
Dynamic groups (Beta CI-46644)
  • Administrators can define the group membership based on attribute criteria that adds or removes members automatically based on the attribute criteria.
  • For more information, see Create and manage dynamic group.
Event based campaigns (isv.beta.CI-45540)
  • If you select Event based campaigns, the instance executes immediately and certify data from the defined events.
  • For more information, see Event based campaigns.
External consent management (CI-131365)
Identity proofing task to the Flow Designer (VDEV-33143)
Identity feed (VDEV-1620)
  • With IBM Verify Identity feed, you can configure and govern identity feed integration to manage employee identities through a human resource management system.
  • For more information, see Managing identity feed.
Inviting users (CI-108233)
  • Create invitations to allow users to create accounts and onboard into Verify. Invitations can be sent, validated, and enforce users create accounts based on the email invitations were originally sent to.
  • For more information, see Inviting users.
Knowledge questions (CIV: Verify Knowledge Questions)
  • Security questions are an older authentication method and are not as secure as other authentication factors. This feature is provided to accommodate the existing requirements of some customers.
  • For more information, see Managing security questions.
Metadata Service self-service (VDEV-52233)
  • Metadata services can be configured to periodically pull a list of metadata documents from an external MDS server and make these available to Verify. These uploaded documents are used to identify and provide additional information for registered FIDO2 authentication devices. It ensures the integrity of devices that are registered by users, as well as provides icons and descriptions for devices.
  • For more information, see Changing the FIDO2 device information .
Orchestration (CI-49771)
  • Use a flow modeler with ready-to-use tasks and decision points to deliver low code / no code administration set up for creating journey time and identity orchestration experiences.
  • For more information, see Managing flow designer.
Profile management (CI-25765)
  • A correlation code can be used in addition to one of the authentication methods. The runtime challenge prompts the user to input the correlation code that is displayed on screen into the IBM Verify app before it approves or denies the verification.
  • For more information, see Configuring authentication factors.
Request access for others (CI-56222)
  • Managers and other permissioned individuals can request access on behalf of their employees or users.
  • For more information, see Requesting Access for Others.
Request access to finer entitlements (CI-35516)
  • Users can request access to fine-grain entitlements, such as Application roles, and specific set of permissions across all the business applications available for them to access. For more information, see Requesting access to finer entitlements.
  • You can customize the Verify request management page for your needs. For more information, see Modify request management pages.
Request access with advance workflow (CI-49772)
Restrict API client management to specific user populations (CI-102537)
  • You can restrict API clients to perform action on specific user populations to reduce the users the API client can act on.
  • For more information, see Creating API clients.
  • Role Recommendations analyzes closed campaigns to identify recurring access patterns and group frequently approved entitlements into predefined roles.
  • For more information, see Role recommendations.
Secrets in CELx expressions (VDEV-66277)
Separating device and user authentication (CI-114829)
User list report (CI-74090)
User scoping enhancement - Condition set filter (VDEV-60004 and VDEV-61485)
  • In the Include only selection, you can use the user scoping enhancements: Fixed set or Condition set tabs to filter the users. With the Fixed set you can search and select multiple users. With the Condition set you can add multiple filter conditions to filter the users. Switching between the Fixed set and Condition set tabs discards all the user selections in the current set.
  • For more information, see Creating a campaign.
Verifiable links (CI-66673)
  • Verifiable links are used to establish digital trust between a website and a mobile app. They allow the platform to verify ownership and delegation so that the OS securely handles certain URLs and the corresponding app without extra user confirmation.
  • For more information, see Verifiable links.