Verint | Telligent Community
Verint | Telligent Community
  • Site
  • User
  • Site
  • Search
  • User
Verint Community 14.x
  • Verint Community
Verint Community 14.x
Developer Training Getting Started
  • User Documentation
  • Ask the Community
  • API Documentation
  • Manager Training
  • Developer Training
  • Tags
  • Sub-Groups
  • More
  • Cancel
  • New
  • Getting Started
  • +External Integration
  • +Plugins/Framework extension
  • +Automations
  • +UI Customization
  • +Notifications and Email
  • +Scripting
  • Obsolescence

Getting Started

The Verint Community platform is developed to enable you to build your own customized community. Beyond the options exposed to configure, layout, and customize a Verint Community-based site using options exposed through the UI for end-users, the platform provides many opportunities to extend and use the platform via custom development as well.

Extensibility Architecture

The architecture of the platform with respect to extensibility and custom development opportunities is outlined below:

With the goal to provide community functionality to your end users, Verint Community provides multiple paths:

  1. UI Customization via UI Extensions, Themes, and Widgets
  2. Automations
  3. Integrated Applications / Plugins
  4. External Applications

UI Customization via UI Extensions, Themes, Widgets, and Embeddables 

The Verint Community primary user experience is delivered through the platform's end-user customizable theming engine that enables drag-and-drop functionality selection, layout options, configuration, and customization using widgets to form web-based experiences. User generated content can make use of embeddables which implement specific formats or functionality within content.

The default experience can be heavily configured through the platform's management features and extended through specific extensibility points. To get started with customizing the UI, see UI Customization.

Automations 

Automations are scripted extensions to Verint Community that can be used to implement business rules and extend the functionality of the platform by handling platform events, running as a background process on a schedule, or being accessible as custom HTTP endpoints. Automations can also provide reusable custom APIs to widgets, themes or other automations.

To get started with implement custom business logic, see Automations.

Integrated Applications / Plugins 

Verint Community enables Microsoft .net developers to integrate with the platform by developing plugins that register directly with the core web and job server implementations for tight and direct integrations and extensions.

All of the core platform functionality (groups, applications, video rendering, API exposure, etc) are built using this plugin architecture. Integrations using plugins are first class citizens in the platform.

To learn more about developing plugin-based integrated applications, see Plugins/Framework extension.

External Applications 

Verint Community enables community exposure limited only by your imagination. Community functionality can be exposed in other web sites and applications and community automation can be implemented via external integrations making use of the REST API and web hooks.

To learn more about integrating with external applications, see External Integration.

The Content Model 

The Verint Community platform provides global social interactions against an abstracted and extensible content model. This model is used regardless of the entry point used for customization or extensibility and is a core concept to development on Verint Community.

  • Created over 1 year ago
Was this helpful?
  • Yes
  • No
  • More
  • Cancel
Recently Updated Articles
  • Article
    Migrate Plugins to Verint Community 14
    Prerequisites How do I install Verint Community? What container images make up Verint Community? Developing a Plugin Overview Verint Community 14 changes how external plugins are created, built, and packaged. Existing plugins should be migrated…
  • Article
    Managing Data Storage
    Often, custom plugins require persistent data storage. While there are many solutions for persistent storage, one option is to use the Verint Community database. Plugins can identify that they need database access and can then install their own schema…
  • Article
    Comments
    The ICommentableContentType plugin type enables comments to be created for your content type. Why should I support comments? When considering social features comments can be a great way to allow users to provide feedback. One example is if you were…
  • Article
    Cookies Authentication
    Cookie Authentication should be used when you have an existing login system which you want to use for the community, and you want your users to be able to sign in once and be logged in to all your websites, rather than having to re-authenticate which…
  • Article
    Unit Testing
    Many teams have adopted some sort of test automation strategy in their development process. This concept can also be applied to custom development on the Verint Community platform. All Verint Community APIs must be run as part of the Verint Community…
Most Helpful Articles
  • Article
    Using Widgets to Render Content From Plugins
    Many plugin types are expected to render content, often HTML content. While this content can be generated completely within code, plugins can also elect to expose some or all of this rendering capability to widgets and optionally allow administrators…
  • Article
    REST Best Practices for Performance
    REST is a powerful tool for integrating external applications with your community. There are aspects to REST that can effect your application performance if you are not conscious of them from the beginning. This guide will help you navigate those hurdles…
  • Article
    Handling Events
    An event is way to react to actions that occur in the platform. Each event executor creates a copy of the content being executed. The In-Process API is used to access the community events. To find out what events are available please see the In-Process…
  • Article
    Factory Default Widget Providers
    Factory default widget providers allow for a logical and physical separation of widgets . Why use Factory Default Providers? Source Control. Each factory provider has a separate folder where its widgets are stored (in the filestorage folder under…
  • Article
    Creating Activity Stories
    Activity stories are shown in the activity stream and provide an easy way for users to stay engaged with a community. Why should I create Activity Stories? When performing actions upon a community providing a stream of events will allow the users…
  • Verint
  • Professional Services
  • Submit a Support Ticket
  • Become a Partner
  • Request a Demo
  • Contact Us

About
Privacy Policy
Terms of use
Copyright 2026 Verint, Inc.
Powered by Verint Community