Micro Office | Extranet & Intranet WordPress Theme
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About Micro Office | Extranet & Intranet WordPress Theme
Intranets die of boredom
Almost all of them follow the same path: built with enthusiasm, filled with sections, the staff come in during the first week and then nobody returns. The tool is not what fails, what fails is that there is no reason to open it on an ordinary Tuesday.
Micro Office is a WordPress theme for intranets and extranets, and it brings the pieces assembled. What decides whether it works is what you put inside.
What it brings
- An internal community with BuddyPress: profiles, groups by department and messaging between colleagues.
- A file repository, so internal documents live in one place rather than in email chains.
- Projects and tasks, with notification panels, calendars and charts.
- Internal training, with courses, quizzes and result tracking.
- Polls, with results presented as graphs.
- Editing with Elementor, for building the screens without coding.
What actually gets people in
It is not the corporate news section. It is the boring things everybody needs: the payslip, the holiday calendar and who has booked what, the canteen menu, the internal phone list, the weekly reports, the expenses form.
If those five things are there and only there, the intranet gets opened every day and then it does make sense to put the community, the training and the polls on top. The other way round does not work: an intranet carrying only nice content does not compete with the chat app the staff already use.
What needs thinking through
Who sees what. An intranet holds staff data, and not everybody should see everything. Groups by department help, but the permissions policy has to be designed rather than improvised, and you have to check that restricted content does not appear in the search or the sitemap.
Keeping it inside. If the site is on the internet, you have to make sure nothing is visible without a session, including the addresses of uploaded files, which in WordPress are reachable by default even when the post is private.
The dependencies. A good part of the features come from third-party plugins, starting with BuddyPress. Worth reviewing which are needed and that they are all current before putting the company's information inside.
Frequently asked questions
Does it need BuddyPress?
Yes, the community, profiles and groups side rests on it.
Is it suitable for training staff?
Yes, it includes courses with quizzes and result tracking.
Can it be used as an extranet with clients?
Yes, that is one of its intended uses, with private areas by group.
What are the pages built with?
With Elementor, with no coding needed.
Topics
Version history
-
v
1.4.2 Current 11 Jun 2024
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.
