Alliance | Intranet & Extranet BuddyPress WordPress Theme

Intranets do not fail on software, they fail on silence

Almost all of them end the same way. They get installed with enthusiasm, three announcements go up the first week, and two months later the latest post is still the director's welcome message. People go back to email and the messaging group, which is where everything actually happens.

The problem is not the theme or the server. It is that an intranet only holds up if there is something inside that the employee needs in order to do their job: payslips, the holiday calendar, the current documents, the directory of who handles what. Without that, it is a noticeboard nobody looks at.

Alliance is a WordPress theme for building that intranet or extranet on BuddyPress, with profiles, groups and activity already solved.

What it contributes

• A corporate intranet structure, with the usual sections already designed.
• BuddyPress profiles and groups, which is what turns a website into a workspace.
• An activity wall for announcements, comments and follow-up.
• Wide customisation options for matching the company's identity.

Intranet and extranet are not the same, and the difference is permissions

The intranet faces inwards: employees, with access to internal information. The extranet faces outwards with a key: customers, suppliers or distributors who come in to see only their own.

That second part is where the expensive mistakes get made. A supplier cannot see the prices you give another one, and a customer cannot see another customer's folder. In BuddyPress everything is visible by default unless you close it, so group separation and profile visibility have to be configured deliberately and then checked by logging in with a test account of each type.

And here is a legal warning that always applies to an intranet: inside it there is personal data belonging to your employees. That brings concrete obligations about who has access, where it is hosted, how long it is kept and what happens when somebody leaves the company. An internal site is not exempt for being internal.

Requirements

It needs WordPress and BuddyPress. Real use also requires serious backups and considered access control, because unlike a public site, what gets lost or leaked here is company documentation.

How to start

One. Decide which specific document is going to make people log in. If there is none, the project is not ready yet.

Two. Build the groups around how the company actually works, not around the org chart. They almost never match.

Three. Log in with an account of each profile and check what it sees. It is the only test that counts.

Four. Name somebody responsible for publishing. An intranet with no owner goes quiet on its own within two months.

Alternatives in the catalogue

Cera and Micro Office cover the same ground with different layouts. Between the three the choice is about appearance and how the sections are organised, because the community engine underneath is the same.

If the project is bigger than it looks and will end up with courses, messaging and a mobile app, the sector's reference is BuddyBoss, which is a whole platform rather than only a theme. It costs more to maintain and takes considerably more.

And if what you want is not a company intranet but an open community of registered users, Ureg is designed for that.

Frequently asked questions

Does it need BuddyPress?
Yes. The profiles, groups and activity come from there; the theme is the presentation layer.

Is it suitable for a customer extranet?
Yes, and it is one of its intended uses, provided you configure the group separation properly.

Are profiles private by default?
No. In BuddyPress visibility gets closed, it does not arrive closed. Worth reviewing before opening up.

Can it be hosted anywhere?
Technically yes, but it holds staff data and that conditions where, and with what backups.

Can it carry the company branding?
Yes, it brings wide options for colours, typography and layout.

What makes an intranet get used?
Something inside it being necessary for working. The design helps afterwards, not before.