Description
Koloshare puts a real intranet inside the WordPress site your business already has. There is no separate hosting to buy and no per-user pricing, and your files and content stay on your server. Files uploaded through Koloshare live in a private folder in your uploads, content lives in your database, and staff sign in on your own address.
It was built for a trade supplier with a warehouse, a trade counter and vans, and it shows: everything is designed to work one-handed on a phone in a van as well as on a desk.
What your team gets, free
- A file library that finds things. Nested folders, drag-and-drop uploads, PDF-first thumbnails, live search across titles and tags, grid and list views, full-screen previews for PDFs, images, video, audio, Word documents and spreadsheets, and one-tap sharing.
- A branded sign-in on your own address, with brute-force lockouts, signed download links and a staff role that cannot reach wp-admin. The full list is under Security below.
What the paid plans add
- A news feed (Standard). One place for everything the company announces, with a pinned lead story, bylines, featured images and department targeting so an article only reaches the teams it concerns. Articles can carry an optional AI-content disclosure.
- Urgent banners (Standard). When something cannot wait, a banner scrolls across the top of every screen until the moment you choose, and arrives without anyone reloading anything.
- A team directory (Standard). Staff cards with photos, departments, quick call and email actions, birthday and work-anniversary badges.
- An external contacts book (Standard). Suppliers, couriers and partners, with per-person contacts under each company.
- A What’s new bell (Standard). New files, articles and Spotlight updates collect in a short list that survives a refresh. Open a row and it opens the item.
- Analytics (Standard). Downloads, views, logins and searches, scoped to intranet users only, with charts, CSV export and a manageable event log.
What the person running it gets
The Command Centre is a single-screen admin app built for people who do not enjoy the WordPress dashboard: files and folders, tags, users, trash and every setting in one place, with the paid sections (news, banners, team, contacts, analytics, branding) appearing there when a plan includes them. A guided setup wizard on first activation gets a working intranet up in about ten minutes.
Security
- A custom branded sign-in; staff credentials are refused at
wp-login.phpand sent to the intranet - Brute-force lockouts with a configurable threshold and duration
- 24-hour temporary passwords that must be replaced on first sign-in
- Signed, time-limited download URLs, so a copied link expires
- Files uploaded through Koloshare kept in a private folder the web server will not serve (on nginx, once the one-line rule Koloshare shows is added), reached through links signed to one person. Files from before 1.8.4 move there with one click, and files a page or post also uses stay public and are listed
- A dedicated Koloshare User role that can use the intranet and cannot reach
wp-admin - Self-healing when a cache serves a logged-in visitor a stale login page
Free, and what the paid plans add
The free Starter tier is the private file library with no cap on it, and it is not a trial: folders, tags, document previews, search, share links, the branded sign-in, all of the security, the setup wizard and the Command Centre. The free plugin contains none of the paid code, so there is nothing in it waiting to be unlocked.
Standard adds the news feed and emailing an article to every account, the What’s new bell, urgent banners in your own colours, the team directory, the contacts book, the homepage background photo, multi-select with bulk download and share, department locks on files, and analytics.
Premium adds custom branding (your logo, colours and a choice of 12 fonts), search inside PDFs and Office documents, a Policies section with sign-off, review dates and a report, induction templates with buddies, optional email tracking and reminder emails, per-file passwords, named-user file visibility, the Spotlight story builder, seasonal decorations, advanced analytics and email support from the Command Centre.
Paid plans are sold per site, one price however many staff sign in, through Freemius. A licence installs the premium version over the top of the free one, sharing every file, setting and user. If it lapses nothing is deleted: the workspace drops back to the free tier, keeps every file and setting, and shows the news, team and contacts again when a licence returns.
Hosting
Koloshare stores everything in your existing WordPress site and does not provide its own backup utility. Before making it your team’s single source of truth, check your hosting plan has enough storage for a growing file library, working automatic backups you have actually tested restoring, and upload limits big enough for your largest files.
Third-party services
The free plugin talks to one outside service. Premium adds a second, and one kind of email to us. All are listed here in full.
Freemius (freemius.com), the licensing and update service. It handles the checkout for paid plans, checks licence status and delivers plugin updates. When you opt in on activation, or activate a licence, it receives what the opt-in screen lists: your WordPress name and email address, the site address, title and language, the WordPress, PHP and Koloshare versions, and whether Koloshare is active. Diagnostic details and your list of plugins and themes are sent only if you leave those boxes ticked. On the free plan you can skip the opt-in and the plugin works the same. Terms: https://freemius.com/terms/ and privacy: https://freemius.com/privacy/
Support email (Premium). If you send a support request from the Command Centre, your site emails it to hello@koloshare.com with the site address, your name and email address, and the Koloshare, WordPress, PHP and theme versions. Nothing is sent unless you press Send.
Google Fonts (Premium). Staff browsers load the workspace font from fonts.googleapis.com and fonts.gstatic.com, Comfortaa by default or the one you choose, so Google sees their IP address. The font picker in the Command Centre and the setup wizard load all twelve fonts to preview them. The free plugin makes no font requests. Privacy: https://policies.google.com/privacy
Everything else the workspace loads (the PDF, spreadsheet, document and chart libraries) ships inside the plugin. See assets/vendor/README.md for what they are and where each came from.
Bundled libraries
These are shipped inside the plugin rather than loaded from a CDN, so the workspace works on a network that cannot reach one and no executable code is fetched from anywhere else. Each is minified as its author distributes it; the unminified source is at the link given, and all are GPL-compatible.
- PDF.js 3.11.174 (
assets/vendor/pdf.min.js,assets/vendor/pdf.worker.min.js) — Apache-2.0 — https://github.com/mozilla/pdf.js - SheetJS Community Edition 0.20.3 (
assets/vendor/xlsx.full.min.js) — Apache-2.0 — https://git.sheetjs.com/sheetjs/sheetjs - JSZip 3.10.1 (
assets/vendor/jszip.min.js) — MIT or GPLv3 — https://github.com/Stuk/jszip - docx-preview (
assets/vendor/docx-preview.min.js) — Apache-2.0 — https://github.com/VolodymyrBaydalka/docxjs
Server tools
If your server happens to have Poppler’s pdftotext installed, Koloshare uses it to pull text out of PDFs for in-document search. Files uploaded in the Command Centre are also read in the browser with the bundled PDF.js, so most sites never need it. Scanned, image-only pages hold no text, so they can’t be searched; Koloshare does no OCR.
None of this is required. Koloshare does not install it, does not ask you to, and falls back to its own PHP reader when it is absent, which handles the PDFs office software, browsers and report generators make. Any document neither can read is counted on Files › Tools, with a button to index it in your browser instead. Where PHP has shell_exec disabled, as it is on plenty of shared hosting, the whole path is skipped and nothing is attempted. Every filename and password handed to pdftotext goes through escapeshellarg().
Installation
- Install and activate Koloshare. You will land in the setup wizard. On a paid plan, activate your licence from your purchase email or under Koloshare → Account; there is no key to type into the plugin.
- Follow the wizard: name your intranet, choose a folder template, and let it create your intranet page. On Premium the wizard also asks for your colours, logo and font.
- If you skip the wizard, create a page, add the
[koloshare_intranet]shortcode and choose the Koloshare (no header) template under Page Attributes. - Add staff on the Command Centre → Staff screen. Each person you invite gets a branded welcome email with a temporary password.
FAQ
Do I need separate hosting?
No. Koloshare runs entirely inside the WordPress site you already have.
Is it priced per user?
No. Paid plans are one price per site, however many staff sign in.
Does my data go anywhere?
Your files, content, staff details and usage stay on your server. Files uploaded through Koloshare sit in a private folder in your uploads and content sits in your database.
Premium can note when an intranet email is opened and when its link is used. It’s off until an administrator turns it on, it uses no outside service, and the record stays in your database for 12 months.
A few things do leave. Freemius, the licensing service, checks a paid licence and receives what its opt-in screen lists. On the free plan that only happens if you opt in. On Premium, staff browsers load the workspace font from Google Fonts, Comfortaa unless you pick another, so Google sees their IP address. And a support request you send from the Command Centre on Premium is emailed to us with your site details. All of it is covered under “Third-party services” below.
What do I actually get for free?
A private file library with no cap on it: folders, tags, previews, search and share links, behind the branded sign-in with all of the security features, the setup wizard and the Command Centre. It is a real intranet, not a demo, and there is no clock on it.
Will it fight with my theme?
It is built not to. Every front-end style is scoped and loaded after the theme, and the bundled page template renders without the theme header and footer so the intranet feels like its own app.
Can staff reach the WordPress dashboard?
No. The Koloshare User role can sign in to the intranet on the front end and is kept out of wp-admin entirely.
How do I get support?
By email, best effort. No response time is guaranteed, and that is stated plainly rather than buried. On Premium you can send it straight from the Command Centre, with your site details attached automatically.
Screenshots







Changelog
1.10.0
- Premium: induction templates. Make one per role and say which departments it suits, and ticking New starter picks the matching ones for you. A template can open in stages from the start date, have a deadline, and include checklist steps for the person or their buddy to tick.
- Premium: change one person’s induction without touching the template, give them a buddy who confirms steps from their own dashboard, and put existing staff on an induction when they change role.
- Premium: Policies has its own Command Centre section for uploads, sections, sign-off settings and the report. Your existing Policies folder stays where it is.
- Premium: a policy can renew on one fixed date a year, have its own review date, and be due by a set date. Ask staff to re-read can set its own sign-by date.
- Premium: the induction report moves to Induction, with a by-template view and two new Excel sheets.
- The Command Centre menu is grouped into Library, Communications, People and Admin. On a phone it’s a section picker.
- Team and Users are now one Staff list. Each person’s profile, Hub sign-in and induction are on one page, and only administrators see the sign-in panel.
- Settings keeps the site-wide options. The hero, dashboard sections and shortcut buttons move to a new Homepage section, banner style to Banners, news authors to News and the file tools to Files.
- WordPress and plugin notices wait behind a button in the header instead of pushing the page down, and dismissed ones stay dismissed.
- Premium: staff with policies to sign see a line under the hero, and a new starter’s induction sits above News.
- Premium: email tracking, off until you turn it on. Clicks and opens have their own switches, tracked emails carry a short note saying so, and the record stays on your site. News posts get a Who’s seen it page, and Staff shows whether someone opened their invite or new password.
- Premium: optional reminder emails. Policies send a daily digest at most and one email when something goes overdue. Inductions send a welcome on the start date, a note to the buddy and one email when overdue. Both start off.
- Premium: each seasonal theme can be switched on or off, given its own dates and set to subtle, normal or festive.
- Inviting someone from Staff now sends their welcome email. Since 1.7.0 the invite created the account but the email never went out.
- Premium: the server reads far more PDFs without extra software, including ones saved from Chrome, and Files › Tools tells you about any it couldn’t read.
- Premium: replacing a file replaces its search text too, so words from the old version stop matching.
- Searching inside documents now runs on Premium only, as the plans have always said. On Standard it was switching itself on by mistake.
- Saving one settings screen no longer resets settings that live on another.
- Premium: a file moved into a restricted folder now takes that folder’s visibility, and files already in one are fixed once when you update.
- The upgrade message for a Premium-only feature now says it needs Premium, not “Standard and Premium”.
1.9.0
- Premium: staff can sign policies with their name, with due dates, yearly renewal and a sign-off report you can export to Excel. On sites updating from an earlier version it starts switched off; turn it on in Settings when you’re ready.
- Premium: a new starter induction checklist, set up in the Command Centre.
- The clear button in the Policies search no longer shows while the box is empty.
1.8.5
- Staff photos, company logos, and news and Spotlight pictures are now stored privately. They only load for signed-in staff who are allowed to see them. Your logo, and pictures used on pages your editors have published, stay public.
- After updating, run Settings → Maintenance → Protect existing files again. It moves older pictures and lists anything that needs your review.
- Fixes two problems in 1.8.4: a file uploaded twice could be stored once, so deleting one copy deleted both, and WordPress embeds could show the titles of private files.
- Freemius SDK updated to 2.13.5.
1.8.4
- Files uploaded in the Command Centre now go into a private folder that the web server will not hand out. Until now they sat in the ordinary uploads folder, where anyone who had the address could open them without signing in. Previews, thumbnails and printing go through a signed link that only works for the person and the image size it was made for, and lapses after a few hours.
- A file picked from the Media Library moves into the private folder the moment it becomes a resource’s file, unless a page, post or your branding also uses it. The edit form says when a file has been left where it is, and why.
- Files added before this version stay where they are until you move them. Command Centre → Settings → Maintenance has a “Protect existing files” button: it counts what would move, copies each file and checks the copy before removing the original, and leaves alone anything a page, post or your branding also uses. Until then administrators see a notice on every admin screen saying how many files are still reachable, and, on a second line, how many stay public because a page, post or setting uses them, with a list of which and why.
- The browser is never handed a file’s real uploads address any more. A password-protected file shows no preview or thumbnail until the password is entered, and policy documents only open in the Policies reader.
- A department download lock is now a lock on the file itself. Outside the department the file shows its title and, at most, a small preview image; it can’t be opened, printed, shared or downloaded, and says so. Staff in the department could not download locked files before either, because the check ran too early to see their department. Both are fixed.
- Searching inside documents no longer matches the text of a file you can’t open: a password-protected file, one limited to named people, or one locked to another department. Adding a password takes a file’s text out of the index straight away.
- WordPress’s own media listing (the REST API, attachment pages, front-end search and sitemaps) no longer shows Koloshare’s files to anyone but managers, the REST API’s list of users is closed to visitors and staff, and numbered author links (?author=1), the users sitemap and oEmbed’s author fields no longer reveal usernames to anyone but managers. The media library still works as before for managers.
- Failed sign-ins are now also counted per address whatever username is typed, so one address can no longer try a password across many usernames. It locks after 20 failures in an hour (or four times the lockout threshold, if that’s higher), on the branded sign-in and wp-login.php alike, and signing in successfully doesn’t reset it.
- Staff accounts are turned away from wp-login.php and sent to the intranet’s own sign-in, a signed-in member of staff who lands there goes straight back to the intranet, and staff accounts can’t use application passwords.
- Someone signed in with a temporary password can only set their own password. Until they do, every file link and workspace request is refused.
- The sign-in and password-request forms carry a security token. A form left open too long asks you to try again rather than failing.
- Opening a file from the Command Centre’s search results shows the right file in the preview and the editor. Before, a result from another folder opened empty.
- On a server running nginx, which ignores the rules Koloshare writes, an administrator sees a notice on Koloshare’s screens with the line to add to the nginx config.
1.8.3
- The two small search bars, “Search in this view” in the file explorer and the Policies search, are back to a sensible size. The Policies one had lost its inner spacing and border to a form reset, which pushed the magnifying glass and the clear button against its edge.
1.8.2
- Publishing news or a banner now goes live straight away. The editor was stamping the article with the browser’s clock, so on a site whose timezone sits behind yours WordPress quietly scheduled it for later and it never appeared. Anything still scheduled shows a “scheduled” badge in the Command Centre.
- Team and Contacts open in a panel that slides in from the right again. A News article still opens in a centred window. On a phone the panel rises from the bottom and can be swiped down to close.
- The What’s new bell and its panel are styled again. An unfinished rule in the stylesheet had been swallowing everything after it.
- The Files tab and the phone tab bar open the file explorer at its top level. Home stays the homepage.
- Homepage shortcut buttons keep a sensible width when there are only one or two of them.
- The action buttons in the Team and Contacts panels no longer lose their bottom edge.
- The read-only pill has gone from the Policies heading.
- Setup wizard: every button is one size, the colour picker fits its card, and the final buttons keep their colours on hover. The title no longer breaks mid-word on a phone.
- Command Centre: search boxes are back to their intended size, the Save button stays on screen under admin notices, the Licence card is spaced like the other cards, the colour picker fits its card, and the app no longer sits 20px wider than the screen.
- Command Centre on a phone: the top bar fits, the New button is reachable, editor buttons wrap instead of running off screen, and the analytics table scrolls inside its card.
- Links inside editors use the workspace colours instead of the WordPress admin blue, and the Bulk Add page no longer shows a garbled Cmd symbol.
1.8.1
- The Team and Contacts sections show in the workspace again on paid plans. A flag the templates checked was never being set, so the nav buttons and the sections behind them stayed hidden.
- The listing and site screenshots are now taken from Isopod Terrarium, the intranet of Isopod Labs, the studio that makes Koloshare.
1.8.0
- Clicking a file opens it straight in the full preview. Search results and shared links do the same, and the separate details panel is gone.
- The preview lists the file’s type, size, last update, download count and folder, then its tags and description. Click the folder name to open that folder.
- The preview’s buttons are Open in new tab, Share and Download. On a phone, Download runs full width under the other two.
- Buttons, cards and tags in the Command Centre no longer lift on hover. Their border and shadow still change.
1.7.2
- The Activity log opens again. Hiding it from the sidebar had unregistered it, so the page refused access and its charts never loaded.
- A site that filters in a self-hosted font no longer warns twice on every page load, and no longer asks Google for a font it does not use.
- Search terms, indexed document text and company contact details are sanitised as soon as they are read.
- The two search-index diagnostics send X-Content-Type-Options: nosniff alongside their plain-text content type.
- Document text is checked with wp_is_valid_utf8() on WordPress 6.9 and later, which replaced the deprecated seems_utf8().
- The setup wizard no longer prints a PHP deprecation above the page. It had been registered without a parent menu, so WordPress had no title to render.
- A fresh install opens the setup wizard again. The licence opt-in screen was consuming the one-shot redirect, so the wizard was silently skipped.
- Settings, Users and the two bulk tools open again. Hiding them from the sidebar had unregistered them, which broke the dashboard links and the password-help email.
1.7.1
- A font name supplied by another plugin through the branding filters is now restricted to what a CSS font-family accepts before it reaches the inline stylesheet.
1.7.0
- The plugin is now called Koloshare. Same plugin, new name: the old one was close enough to an unrelated project’s to cause confusion.
- The free plugin no longer carries any licence or plan machinery. There is no licence key field, no feature table and no upgrade prompts. Everything it ships is simply available. Paid features live in a separate plugin, as they already did.
- The setup wizard drops its licence step. It now runs welcome, name, folders, intranet page, done.
- The remaining inline script and stylesheet blocks are enqueued through the WordPress asset API.
- The two administration tools for rebuilding the search index are signed now, in line with the others.
1.6.2
- Fixed: on the free plan, Continue on the setup wizard’s “Logo & font” step reported that nothing had saved. The step is Premium-only and had nothing to save, but the free build had no handler answering it at all, so the wizard treated the empty reply as a failure. Skip was unaffected.
- Renaming a tag across the library no longer asks the database to count the rows it is about to rewrite.
- Housekeeping: a development-only patch file from the licensing SDK is no longer included in the download.
1.6.1
- The What’s new bell is now part of Standard and Premium. It rings for new files, articles and Spotlight updates, and the articles and updates come with a paid plan, so the bell belongs with them.
- Seasonal decorations are now a Premium feature, and they work: a switch in Settings turns them on, a preview picker forces one theme for checking, and each person can turn them off from their account menu. The layer shipped in earlier versions without any way to switch it on.
- Nothing else on the free tier has changed.
1.6.0
- The free tier is now the file library with no cap on it. The ten-file limit has gone.
- Paid features ship in a separate premium version, installed through your Koloshare account when a licence is activated, rather than sitting locked inside the free plugin. The free plugin contains no paid code and makes no request to any outside service.
- The news feed, email broadcast and analytics move to Standard. On a free site, existing articles, team members and contacts stay in the database and are shown again the moment a licence is activated. Nothing is deleted.
- Free sites update in place. Paying sites are offered the premium version from the Plugins screen or their Koloshare account; installing it carries over every file, setting and user.
1.5.5
- Admin maintenance links (clear lockouts, re-run the search index, re-run setup) are signed now. They acted on a plain web address before, which meant an administrator could be made to fire one by following a link.
- The document-index diagnostic page is development-only, and no longer accepts a document password in the address bar, where it would have been written to the server log.
- Failed sign-ins are no longer written to the server log with the username attached.
- Documented what the plugin talks to and what it does with server tools like pdftotext, and where every bundled library came from.
1.5.4
- Six ready-made Spotlight arrangements instead of four, between them showing every block the builder offers. The recruitment one has gone: it only made sense to someone who did not work there yet.
- The arrangement picker fits the editor again. It was laid out in columns wider than the space it had, so the third one sat under the inspector panel.
1.5.3
- Spotlight introductions are centred again, and consecutive paragraphs have space between them. A typography reset was overriding both.
1.5.2
- The What’s new bell rings again when a file is replaced. Swapping the document behind an existing entry counts as news; renaming, retagging or moving it still does not.
1.5.0
- Every third-party library now ships with the plugin instead of loading from a CDN. PDF.js and its worker, JSZip, Chart.js and docx-preview join SheetJS in the plugin itself, so the workspace works on a network that cannot reach a CDN and no executable code is fetched from anywhere else.
- The Starter upgrade reminder appears only on Koloshare’s own screens, can be dismissed, and stays dismissed.
- The setup wizard no longer asks for a licence key it cannot use. Where the licence is managed by your Koloshare account, the wizard says so and links to it instead.
Older entries are in changelog.txt, alongside the plugin.
