The portal's features belong to plugins, not to ThemeREX
Alliance is sold as an intranet and extranet theme, and the demo dashboards — events, notifications, calendars, corporate graphs, news — look like one product. Read the vendor's own feature breakdown and the internals belong to other people's plugins. Groups and departments come from BuddyPress, threaded discussion from bbPress, file sharing from Knowledge Base for Documents and FAQs, polls from Democracy Poll, poll charts from M Chart with the Highcharts library, courses and quizzes from LearnDash.
That shapes the buying decision more than any layout question. You are buying a styled, preconfigured wrapper: page layouts, theme options and plugin styling. Who can create a group, whether forums are private, how a document library is permissioned — all of that is configured in those plugins, follows their update cycles and carries their licence terms. Alliance has no separate intranet engine of its own, and the vendor does not claim one.
Version 3 swapped WPBakery for Elementor and rewired the plugin stack
If you are taking over an existing Alliance site, the 26 December 2022 version 3.0 entry in the changelog matters more than any recent release note. It lists WPBakery Page Builder under removed, along with Essential Grid, Booked Appointments, BuddyDrive, Event Organiser, Responsive Poll and WP-Pro-Quiz, and puts Elementor, BuddyPress Docs, BuddyPress for LearnDash, Knowledge Base for Documents and FAQs, Democracy Poll, rtMedia, The Events Calendar, WP Job Manager and LearnDash LMS under added.
The vendor's source text carries an explicit instruction to read a dedicated article before updating from version 2 to version 3. That warning is worth heeding for the structural reason behind it: content laid out in WPBakery does not become Elementor content because a newer theme build is installed, and documents or polls that lived in BuddyDrive or Responsive Poll are now expected in different plugins. A live internal site carries a migration project inside that version number, not a routine update.
Everything since has been maintenance-shaped. Entries alternate between core-file updates and revisions to the default skin, with occasional translation-string and style additions, plus a LearnPress compatibility mention and an Online Learning homepage in 3.9.0. None of it signals a new portal capability, so a theme you install today behaves like the version 3 line, not like a new product.
Inheritance and overrides are the theme's own contribution
The one capability the vendor describes as unique to Alliance is its settings system: inheritance and override options that let you set individual parameters per section of the site and per supported plugin. Practically, that means one global setting supplies the default and a department page or section can deviate without you rebuilding its neighbours. In an intranet where a dozen departmental areas each want slightly different headers or typography, that is the control that saves repeated work, and it is the feature to evaluate first if you are comparing Alliance with a generic corporate theme.
Around it sit the framework items the vendor lists: 750+ Customizer options, custom post types, custom widget sets, custom shortcodes and a theme options panel. Headers and footers are built in Elementor rather than fixed in template files, so changing the top navigation or the footer arrangement is an editing task, not a code change. The theme is marked widget ready, Gutenberg optimized and high resolution, with PHP, CSS and JavaScript among the included file types.
Where each portal function actually gets configured
Groups and departments run on BuddyPress's group component, with Better Messages for private messaging, rtMedia for media uploads and BuddyPress Docs for shared documents named alongside. If your organisation already runs BuddyPress, note that the declared compatibility covers 9.x.x and 10.x.x only; nothing newer is claimed.
Documents are the Knowledge Base plugin's content, sitting where that plugin puts them rather than in a theme panel. Poll results depend on M Chart for rendering, so if charts are how you report survey findings, check the chart types M Chart offers before committing. Courses are LearnDash's, with LearnDash LMS Course Grid and BuddyPress for LearnDash listed; paid courses imply WooCommerce or a membership plugin, and Paid Memberships Pro and elegro Crypto Payment appear in the vendor's list for exactly that reason. Job listings and resumes — the reason the theme is filed under corporate/directory-listings — come from WP Job Manager and its Resume Manager add-on.
That is a wide stack. An intranet that only needs news, documents and a staff directory could run on far fewer of these plugins, with fewer settings screens and a shorter update path to maintain.
The demo images are not part of the theme
A one-click demo installation and Slider Revolution and Swiper sliders are listed among the theme's features, and detailed documentation and regular updates are vendor claims. The vendor also states plainly that all images are copyrighted to their respective owners and that preview images are not included in the template. The demo dashboards read as convincing largely because of that photography; plan to supply your own staff and office imagery, or the imported site will not resemble the preview.
Compatibility declarations recorded in November 2026
The marketplace attributes observed on 4 November 2026 list WordPress 4.9.x through 7.0.x, BuddyPress 9.x.x and 10.x.x, bbPress 2.5.x and 2.6.x, Elementor and Elementor Pro, Events Calendar, WooCommerce 5.x.x and 6.x.x, and WPML, with Chrome, Firefox, Safari, Opera and Edge named as browsers. These are vendor declarations, not records of testing on a particular install. The WooCommerce and BuddyPress ranges in particular sit well behind current releases, so treat your own plugin versions as a staging question rather than something an attribute list answers.
Questions & answers
Does Alliance provide an intranet without BuddyPress installed?
The community, group and department features are described as built on BuddyPress and bbPress, so those functions depend on the plugins being present. Pages, Elementor layouts and the Elementor-built headers and footers do not, but the portal features the theme markets do.
Can I keep an old WPBakery-built Alliance site after updating?
Version 3.0, released 26 December 2022, removed WPBakery Page Builder and added Elementor, and several community plugins changed at the same time. Content built in WPBakery does not convert automatically, and the vendor directs version 2 users to a dedicated migration article before updating.
Where is the setting that differs between pages and sections?
The vendor's inheritance and override system is the theme-level control for that. A global setting acts as the default and an individual section or page can override it, which is the intended way to give departmental areas their own parameters without duplicating the rest.
